summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorFelix Blyakher <felixb@sgi.com>2008-07-15 21:40:22 +0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2008-07-16 02:08:59 +0400
commitd67d1c7bf948341fd8678c8e337ec27f4b46b206 (patch)
tree69bec2c4fcabba993fea54f9d3be26963f9f13ce /fs
parentc2e1b09ff237c0a3687b9a804cc8bf489743cffc (diff)
downloadlinux-d67d1c7bf948341fd8678c8e337ec27f4b46b206.tar.xz
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>
Diffstat (limited to 'fs')
-rw-r--r--fs/lockd/clntproc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/lockd/clntproc.c b/fs/lockd/clntproc.c
index 5df517b81f3f..fd7d4669776e 100644
--- a/fs/lockd/clntproc.c
+++ b/fs/lockd/clntproc.c
@@ -430,7 +430,7 @@ nlmclnt_test(struct nlm_rqst *req, struct file_lock *fl)
* Report the conflicting lock back to the application.
*/
fl->fl_start = req->a_res.lock.fl.fl_start;
- fl->fl_end = req->a_res.lock.fl.fl_start;
+ fl->fl_end = req->a_res.lock.fl.fl_end;
fl->fl_type = req->a_res.lock.fl.fl_type;
fl->fl_pid = 0;
break;