From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 04:13:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 898C216A4CE; Tue, 11 Nov 2003 04:13:35 -0800 (PST) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6447743FB1; Tue, 11 Nov 2003 04:13:34 -0800 (PST) (envelope-from l.ertl@univie.ac.at) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) hABCDJNo187082; Tue, 11 Nov 2003 13:13:25 +0100 Date: Tue, 11 Nov 2003 13:13:19 +0100 (CET) From: Lukas Ertl To: Don Lewis In-Reply-To: <200311102232.hAAMW2eF067714@gw.catspoiler.org> Message-ID: <20031111130545.H53345@pcle2.cc.univie.ac.at> References: <200311102232.hAAMW2eF067714@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mx1 4261; Body=0 Fuz1=0 Fuz2=0 cc: current@FreeBSD.org Subject: Re: named pipes memory leak? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 12:13:35 -0000 On Mon, 10 Nov 2003, Don Lewis wrote: > On 10 Nov, Lukas Ertl wrote: > > On Mon, 10 Nov 2003, Don Lewis wrote: > >> > >> If fifo_open() is interrupted, fifo_close() never gets called, and the > >> resources are not recovered. I wish doing the resource recovery in > >> fifo_inactive() would have worked ... > >> > >> Try this patch: > > > > Thanks, your patch seems so solve this problem effectively. > > The patch has been committed. Thanks for testing it. Unfortunately, we are still seeing a problem here: we are running uvscan (virus scanner), and while running it we are still seeing increasing unpcb usage and orphaned unix domain sockets. We added some debug printfs to the fifo routines and found out that fifo_cleanup is called from fifo_close with a vnode which has v_usecount == 2 so the socket close calls aren't reached. Any ideas? regards, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/