Date: Tue, 17 Aug 2004 14:42:34 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Alfred Perlstein <alfred@freebsd.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/fs/pseudofs pseudofs_vncache.c Message-ID: <xzp657iszph.fsf@dwp.des.no> In-Reply-To: <20040816232714.GE57908@elvis.mu.org> (Alfred Perlstein's message of "Mon, 16 Aug 2004 16:27:14 -0700") References: <200408152158.i7FLw2mW016740@repoman.freebsd.org> <20040816073314.GA57908@elvis.mu.org> <xzp657jmlqn.fsf@dwp.des.no> <20040816232714.GE57908@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein <alfred@freebsd.org> writes: > Maybe I'm missing some external references that can reactivate them? If someone tries to access the file while it is being removed, pfs_vncache_alloc() will create a new vnode since the old one is no longer in the cache, and possibly overwrite the vnode pointer in the pfs_node before the old vnode is released, leading to a leaked vnode. > If so those could be prevented by flagging the node. You're right, I didn't think of that. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp657iszph.fsf>