From owner-freebsd-bugs@FreeBSD.ORG  Mon Apr 25 15:50:23 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 409B216A4CE
	for <freebsd-bugs@hub.freebsd.org>;
	Mon, 25 Apr 2005 15:50:23 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 24C9743D31
	for <freebsd-bugs@hub.freebsd.org>;
	Mon, 25 Apr 2005 15:50:23 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3PFoNFU098502
	for <freebsd-bugs@freefall.freebsd.org>; Mon, 25 Apr 2005 15:50:23 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3PFoM17098501;
	Mon, 25 Apr 2005 15:50:22 GMT
	(envelope-from gnats)
Date: Mon, 25 Apr 2005 15:50:22 GMT
Message-Id: <200504251550.j3PFoM17098501@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
Subject: Re: kern/80322: TCP socket support broken on a busy port
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2005 15:50:23 -0000

The following reply was made to PR kern/80322; it has been noted by GNATS.

From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
To: Jan Srzednicki <w@expro.pl>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/80322: TCP socket support broken on a busy port
Date: Mon, 25 Apr 2005 17:42:57 +0200

 On Mon, Apr 25, 2005 at 02:16:50PM +0200, Jan Srzednicki wrote:
 
 > After a server daemon listening on a very busy unprivileged (>1024) port
 > dies (I'm not able to repeat that with a low-usage port), the port is
 > closed as it should, sockstat doesn't show anything listening on it,
 > everything looks fine. But an attempt to bind to that port with UID != 0
 > results in failure -- EADDRINUSE.
 
 Hm, I saw behaviour like this on 4.8 machine running some shoutcast
 server; after killing radio process it was unable to bind to port
 as if it was already open (nothing was listening on it) but after
 a minute or so it was able to bind again. I've never investigated
 this.
 
 
 -- 
 Paweł Małachowski