Date: Wed, 31 Oct 2001 01:10:01 -0800 (PST) From: Mail Administration <mail@twwells.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/31647: socket calls can return undocumented EINVAL Message-ID: <200110310910.f9V9A1Z17511@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/31647; it has been noted by GNATS. From: Mail Administration <mail@twwells.com> To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Cc: toor@twwells.com (Bourne-again Superuser), FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/31647: socket calls can return undocumented EINVAL Date: Wed, 31 Oct 2001 02:59:39 -0600 (CST) > <<On Tue, 30 Oct 2001 15:42:06 -0600, Bourne-again Superuser <toor@twwells.com> said: > > A rather large number of tcp routines begin with > > COMMON_START(), which can cause them to return EINVAL when > > inp_ppcb is null. > > This is supposed to be a ``can't happen'' condition. Just to be sure, I cvsupped to -stable tonight and tried again. I am able to reliably get shutdown() to return EINVAL when its "how" parameter is SHUT_WR. So unless there's somewhere else that it can return EINVAL, this "can't happen" actually does happen. Is there anything I might do that would be useful in tracking down the problem? 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?200110310910.f9V9A1Z17511>