Date: Mon, 3 Dec 2001 22:49:13 -0800 (PST) From: Archie Cobbs <archie@dellroad.org> To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: differing behavior of connect(2) in -current? Message-ID: <200112040649.fB46nD781640@arch20m.dellroad.org>
next in thread | raw e-mail | index | archive | help
Hi, We're seeing strange behavior of mpd (netgraph-ified ppp daemon) under -current that doesn't occur under -stable. The problem is that when mpd tries to do a connect(2) on a (PF_INET, SOCK_RAW, IPPROTO_GRE), the kernel returns EINPROGRESS instead of succeeding immediately (note: this is a datagram socket so a connect should succeed immediately). The only catch is that the connect(2) is being done in the kernel by a ng_ksocket(4) node instead of via the normal system call. The ng_ksocket(4) calls soconnect() to perform the connect. I've tried reproducing the same problem with userland code but it doesn't seem to happen. So maybe this is a result of the different threading model in the -current kernel? Any ideas appreciated. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112040649.fB46nD781640>