Hi,
This patch sets up a list of locks held by a client (associated with a host).
Then, when the client gets a granted lock it can respond positively if he
holds allready the lock. This fixes a bug I described previously.
Some remarks:
- the locks are added and deleted based on the callbacks invoked from the file
locking systems when a lock is inserted or removed
(nlmclnt_insert_lock_callback...)
- a semaphore protects the list. I don't know if it is usefull, nor harmfull
(may it deadlock ?), but I set it up such that I don't have to bother with
simultaneous access.
- I use the linux lists.h. It is not needed to have doubly linked lists, but I
thought I would introduce less bugs than if I did my own.
- I did these lists because posix_test_lock wasn't really fine to detect that
the lock was allready held. However, I really decided to do it when I saw:
* FIXME: In 2.5 we don't want to iterate through any global file_lock_list.
* Maintain NLM lock reclaiming lists in the nlm_host instead.
I think this patch implements such a list. Has anybody implemented the same
thing ?
I haven't done the changes to the code actually doing the reclaiming, because
I can't test crashing (I test everything on a single host). I could do the
code, but can't test. Interested ?
Pat
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Here is the patch ;-)
Pat