Subject: Re: vnode changes & 1.4E
To: Chris G. Demetriou <cgd@netbsd.org>
From: Bill Studenmund <wrstuden@nas.nasa.gov>
List: current-users
Date: 07/08/1999 13:02:34
On 7 Jul 1999, Chris G. Demetriou wrote:

> "Aaron J. Grier" <agrier@poofy.goof.com> writes:
> > > Right now the only filesystems which are unchanged are unionfs and nfs.
> > > nfs does no locking right now, and adding it would be a big mess.
> > 
> > How big of a mess?
> > 
> > > We need to, but I don't have time.
> > 
> > No kidding... even linux does NFS locking nowadays.  ;)

I haven't reviewed the paper, but NFS locking, a la lockd, has been
mathematically proven to be flawed. If locking's a super concern, you
don't want NFS. :-)

> Uh, NFS locking (rpc.lockd, etc.) is Different than what's being
> talked about here, unless i'm ... badly mistaken.

You are 100% correct. I'm talking about locking the vnode, not NFS
locking.

The problem is that a lot of operations start with the vnode locked. We
need to come up with a way to unlock the vnode during an rpc, and then
re-lock it when the rpc response is received. I'm not up to speed enough
w/ NFS to do this.

Take care,

Bill