Subject: Re: vnode locking procedure change to suport stacked fs's.
To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
From: Bill Studenmund <wrstuden@nas.nasa.gov>
List: tech-kern
Date: 06/01/1999 11:38:36
On Tue, 1 Jun 1999, Bill Sommerfeld wrote:

> > Touch a file Makefile (vnode A) in /a, with lower vnode B in /usr.
> > Then touch Makefile in /c (vnode C).  Now both A and C have the same
> > lower vnode.  This is fine, unless during the creation of C,
> > the vnode that getnewvnode() finds to make it is A.  
> 
> This case could be fixed/worked around by changing getnewvnode() to
> skip locked vnodes on the freelist.

My thought was to just have getnewvnode() ignore the previous contents of
v_vnlock (the pointer)  and initialize it to &vp->v_lock (the struct
lock). 

Take care,

Bill