Felix Blyakher d67d1c7bf9 nfs: set correct fl_len in nlmclnt_test() ... fcntl(F_GETLK) on an nfs client incorrectly returns the values for the conflicting lock. fl_len value is always 1. If the conflicting lock is (0, 4095) the F_GETLK request for (1024, 10) returns (0, 1), which doesn't even cover the requested range, and is quite confusing. The fix is trivial, set fl_end from the fl_end value recieved from the nfs server. Signed-off-by: Felix Blyakher <felixb@sgi.com> Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>		2008-07-15 18:08:59 -04:00
..
clntlock.c
clntproc.c	nfs: set correct fl_len in nlmclnt_test()	2008-07-15 18:08:59 -04:00
host.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	2008-04-24 11:46:16 -07:00
Makefile
mon.c
svc.c	Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6	2008-04-24 11:46:16 -07:00
svc4proc.c
svclock.c	fs: replace remaining __FUNCTION__ occurrences	2008-04-30 08:29:54 -07:00
svcproc.c
svcshare.c	lockd: fix sparse warning in svcshare.c	2008-04-23 16:13:39 -04:00
svcsubs.c	lockd: unlock lockd locks held for a certain filesystem	2008-04-25 13:00:11 -04:00
xdr.c
xdr4.c