summaryrefslogtreecommitdiffstats
path: root/fs/nfs
diff options
context:
space:
mode:
authorFelix Blyakher <felixb@sgi.com>2008-07-15 12:40:22 -0500
committerTrond Myklebust <Trond.Myklebust@netapp.com>2008-07-15 18:08:59 -0400
commitd67d1c7bf948341fd8678c8e337ec27f4b46b206 (patch)
tree69bec2c4fcabba993fea54f9d3be26963f9f13ce /fs/nfs
parentc2e1b09ff237c0a3687b9a804cc8bf489743cffc (diff)
downloadop-kernel-dev-d67d1c7bf948341fd8678c8e337ec27f4b46b206.zip
op-kernel-dev-d67d1c7bf948341fd8678c8e337ec27f4b46b206.tar.gz
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/nfs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud