From owner-freebsd-hackers Sat Apr 5 12:59:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA27305 for hackers-outgoing; Sat, 5 Apr 1997 12:59:53 -0800 (PST) Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA27300 for ; Sat, 5 Apr 1997 12:59:49 -0800 (PST) Received: from idt.unit.no (26850@kamelia.idt.unit.no [129.241.111.27]) by pat.idt.unit.no (8.8.5/8.8.5) with ESMTP id WAA06400; Sat, 5 Apr 1997 22:56:11 +0200 (MET DST) Message-Id: <199704052056.WAA06400@pat.idt.unit.no> To: terry@lambert.org Cc: dfr@nlsystems.com, dg@root.com, ponds!rivers@dg-rtp.dg.com, freebsd-hackers@freebsd.org Subject: Re: kern/3184: vnodes are used after they are freed. (dup alloc?) In-Reply-To: Your message of "Sat, 5 Apr 1997 13:03:20 -0700 (MST)" References: <199704052003.NAA23438@phaeton.artisoft.com> X-Mailer: Mew version 1.06 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 05 Apr 1997 22:56:08 +0200 From: Tor Egge Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > - Let getnewvnode call VOP_ISLOCKED and skip locked nodes on the > > so-called free list. > > There's no holder, so it isn't locked. If it were locked via VOP_LOCK, > then you wouldn'r be having this problem in the first place, since a > VOP_LOCK will prevent a node from being vclean()'ed (that's the whole > point of the NFS changes Doug has been trying to deal with, if you > followed his postings on them). Wrong. Under some circumstances, the vnode is locked. See the end of vputrele. - Tor Egge