summaryrefslogtreecommitdiffstats
path: root/fs/nfs/nfs4_fs.h
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2009-07-21 16:47:46 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2009-07-21 16:47:46 -0400
commitb64aec8d1e1d8482a7b6cca60c8105c756bf1fe4 (patch)
tree022958ab88c3e6a7c9372e50cedb588e73462b57 /fs/nfs/nfs4_fs.h
parentaea1f7964ae6cba5eb419a958956deb9016b3341 (diff)
downloadlinux-b64aec8d1e1d8482a7b6cca60c8105c756bf1fe4.tar.gz
linux-b64aec8d1e1d8482a7b6cca60c8105c756bf1fe4.tar.bz2
linux-b64aec8d1e1d8482a7b6cca60c8105c756bf1fe4.zip
NFSv4: Fix an Oops in nfs4_free_lock_state
The oops http://www.kerneloops.org/raw.php?rawid=537858&msgid= appears to be due to the nfs4_lock_state->ls_state field being uninitialised. This happens if the call to nfs4_free_lock_state() is triggered at the end of nfs4_get_lock_state(). The fix is to move the initialisation of ls_state into the allocator. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs/nfs4_fs.h')
0 files changed, 0 insertions, 0 deletions