From owner-freebsd-hackers Sun Apr 18 4:32:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 4EF7E150AF for ; Sun, 18 Apr 1999 04:32:21 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA31727 for ; Sun, 18 Apr 1999 07:29:57 -0400 (EDT) Date: Sun, 18 Apr 1999 07:29:57 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: LinuxThreads doesn't fdfree? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me, or at kern_exit.c:441, I notice that fd's are never freed? This can cause problems (of course leaked memory) such as a socket remaining open when a process exits! That can definitely lead to a panic. Now, can someone evaluate all of the code Dick added around exit() and wait() (mach dep too), and at least tell me if I'm right about this. fdfree() shouldn't free fd in this case, but shouldn't we at least be decrementing the refcnt? Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message