From owner-freebsd-bugs Wed Oct 31 1:10: 5 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EB77437B403 for ; Wed, 31 Oct 2001 01:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9V9A1Z17511; Wed, 31 Oct 2001 01:10:01 -0800 (PST) (envelope-from gnats) Date: Wed, 31 Oct 2001 01:10:01 -0800 (PST) Message-Id: <200110310910.f9V9A1Z17511@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mail Administration Subject: Re: kern/31647: socket calls can return undocumented EINVAL Reply-To: Mail Administration Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/31647; it has been noted by GNATS. From: Mail Administration 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) > < 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