NFSv4: Fix an Oops in nfs4_free_lock_state
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 21 Jul 2009 20:47:46 +0000 (16:47 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 21 Jul 2009 20:47:46 +0000 (16:47 -0400)
commitb64aec8d1e1d8482a7b6cca60c8105c756bf1fe4
tree022958ab88c3e6a7c9372e50cedb588e73462b57
parentaea1f7964ae6cba5eb419a958956deb9016b3341
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>
fs/nfs/nfs4state.c