From owner-freebsd-hackers Tue Jul 25 14: 9: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 7C87837B95C for ; Tue, 25 Jul 2000 14:08:56 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA13311; Tue, 25 Jul 2000 14:08:54 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200007252108.OAA13311@bubba.whistle.com> Subject: Re: odd accept(2) behavior In-Reply-To: <20000725193916.37721.qmail@hotmail.com> from Greg Thompson at "Jul 25, 2000 03:39:16 pm" To: Greg Thompson Date: Tue, 25 Jul 2000 14:08:54 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Thompson writes: > i'm seeing some fairly odd behavior from accept(2) when the connecting > socket goes away at just the right time. the timing is fairly funky, so i > don't know if i can easily whip up a repro for this, but what i'm seeing is: > > accept returns a positive value (ie: not an error), but sets the addrlen to > zero. a subsequent call to getsockname with the new socket returns -1 and > sets errno to ECONNRESET. Everything sounds normal/expected except the part about addrlen being set to zero. That sounds like a bug. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message