From owner-freebsd-bugs  Mon Apr 10  2:40: 8 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id B23F337B845
	for <freebsd-bugs@FreeBSD.org>; Mon, 10 Apr 2000 02:40:03 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id CAA39254;
	Mon, 10 Apr 2000 02:40:03 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4])
	by hub.freebsd.org (Postfix) with ESMTP id 4BE7C37B751
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Apr 2000 02:31:53 -0700 (PDT)
	(envelope-from root@niw.com.au)
Received: by rose.niw.com.au (Postfix, from userid 0)
	id 70F1562D12; Mon, 10 Apr 2000 19:01:49 +0930 (CST)
Message-Id: <20000410093149.70F1562D12@rose.niw.com.au>
Date: Mon, 10 Apr 2000 19:01:49 +0930 (CST)
From: ian@niw.com.au
Reply-To: ian@niw.com.au
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/17895: stale unix domain connections
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         17895
>Category:       kern
>Synopsis:       stale unix domain connections
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 10 02:40:02 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Ian West
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
SMP kernel, dual PIII-450, 256Megs Memory.

>Description:
Poorly written (alpha) code which opens a unix domain listener socket,
but which fail's to 'attach' in combination with a client attached to
this, can leave open connections which do not appear to time out when
the socket is closed due to a terminate.

I would guess that if enough of these were left laying around it could
eventually chew up enough resouces to cause problems.

netstat -an output follows

cde970c0 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde97140 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde97d80 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde97f00 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde97180 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde974c0 stream   12   0   0   0   0   0 /home/ian/tools/testsocket
cde97640 stream    0   0   0   0   0   0 /home/ian/tools/testsocket
cde978c0 stream    1   0   0   0   0   0 /home/ian/tools/testsocket


>How-To-Repeat:
Open a unix domain socket for listen. Connect to it from a another
program, terminate the listener before the connection has been
'accepted' The connection seems to remain.

>Fix:
Unknown at this stage. I suspect a check needs to be made on
exit for open unix domain sockets ? Where are ipv4 domain sockets
checked ? do they just wait for a timeout ?


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message