From owner-freebsd-bugs Wed Oct 31 13:50: 8 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 8D64E37B406 for ; Wed, 31 Oct 2001 13:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9VLo2784188; Wed, 31 Oct 2001 13:50:02 -0800 (PST) (envelope-from gnats) Date: Wed, 31 Oct 2001 13:50:02 -0800 (PST) Message-Id: <200110312150.f9VLo2784188@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: mail@twwells.com (Mail Administration), FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/31647: socket calls can return undocumented EINVAL Date: Wed, 31 Oct 2001 15:41:53 -0600 (CST) > < said: > > 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. > > > Is there anything I might do that would be useful in tracking down > > the problem? > > Please provide the procedure or scenario you used to reproduce the > problem. There are three pieces: apache, my program, and ab. I set them all up on one machine so I could stress test the program. The only odd things I've done on the test machine are to set all file systems noatime and net.inet.tcp.msl=100. That latter, to keep the system from having too many TIME_WAIT connections. My program is functioning as a TCP proxy between ab and apache; I simply start ab with a URL pointing to the proxy's port and it redirects the session to apache. (They're all using 127.0.0.1, in case that's significant.) I don't get a failure immediately or at a specific time but I'm pretty much guaranteed to get a failure reasonably quickly. The failure is in the proxy itself. If I make the proxy ignore the error, everything works as expected. I was able to ktrace a failure. It shows a successful writev() to the client socket immediately followed by a shutdown() that returns EINVAL. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message