Re: Linux' NFS locking b0rken?

[Olaf Kirch <okir@suse.de>]

On Tue, May 25, 2004 at 06:11:08PM -0400, Trond Myklebust wrote:
> Any program which relies on the fact that BSD locks are inherited by
> child processes will fail to work correctly with you wrapper (because
> fcntl() locks are not inherited).

Shouldn't it be possible to map flock locks onto the NLM interface
if we simply record the PID of the process originally requesting
the lock, and reuse that pid in all future operations? All the
flock semantics are provided by fs/locks.c already; all the
NLM client needs to do is to formulate appropriate NLM calls
for lock type changes (SH->EX and vice versa), and unlocks.

Really the only gotcha is that subsequent calls on an existing
lock use the same PID as the original call, so that the server
lockd can match up the request with its existing list of locks.

Olaf
-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs