Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Apr 1997 14:14:39 -0700 (MST)
From:      Terry Lambert <terry@lambert.org>
To:        Tor.Egge@idi.ntnu.no (Tor Egge)
Cc:        terry@lambert.org, 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?)
Message-ID:  <199704052114.OAA23667@phaeton.artisoft.com>
In-Reply-To: <199704052056.WAA06400@pat.idt.unit.no> from "Tor Egge" at Apr 5, 97 10:56:08 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> > >   - 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.

I should have said that there's no *guarantee* that there is a holder
or that it is locked.  The approach will fix some circumstances, but
will fail for others without the *guarantee*.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704052114.OAA23667>