Date: Fri, 16 Nov 2001 18:50:01 -0800 (PST) From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/31746: failed connect(2) seems to cause problems with socket Message-ID: <200111170250.fAH2o1E49428@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/31746; it has been noted by GNATS. From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: <freebsd-gnats-submit@FreeBSD.org>, <bachue@bachue.com> Cc: Subject: Re: kern/31746: failed connect(2) seems to cause problems with socket Date: Fri, 16 Nov 2001 21:42:12 -0500 I've hacked away at this for a bit, and it seems that during the first call, something NULLs out so_pcb. This makes the COMMON_START macro (see netinet/tcp_usrreq.c) fail out with EINVAL, and since tcp_connect() uses the COMMON_START macro, any subsequent connect() will fail with EINVAL instead of ECONNREFUSED. The in_pcbdetach() and in_pcbdisconnect() routines seem to be likely culprits, and I'm currently tracking down where one of these functions may be called in error. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111170250.fAH2o1E49428>