From: Marc Eshel <eshel@almaden.ibm.com>
Subject: Re: [patch] flock/fcntl bug
Date: Wed, 15 Dec 2004 18:16:42 -0800
Message-ID: <OFDB90A431.EDCAD4C3-ON88256F6C.000B5989-88256F6C.000C8438@us.ibm.com>
References: <1103157295.1236.70.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Cc: nfs@lists.sourceforge.net
In-Reply-To: <1103157295.1236.70.camel@lade.trondhjem.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net


Trond Myklebust <trond.myklebust@fys.uio.no> wrote on 12/15/2004 04:34:55
PM:

> > It would be nice if it didn't have to care but the fact is that right
now
> > there is dependency on the lock state to be in the VFS too for correct
> > operation.

> Then fix the VFS to do the right thing. Move the decision about whether
> or not to do an RPC call or whatever into the filesystem where it
> belongs.

I will be glad to. Please add my patch 'locking for cluster filesystem' so
other users can experiment with their favorite file system and give some
feed back. My patch is getting too big and it is a pain to retrofit it to
constantly changing code. It will than be easier to build small patches for
the specific problem that will arise.

Thanks, Marc.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs