nfsd: fix bug on nfs4 stateid deallocation
authorycnian@gmail.com <ycnian@gmail.com>
Mon, 11 Mar 2013 00:46:14 +0000 (08:46 +0800)
committerJ. Bruce Fields <bfields@redhat.com>
Wed, 3 Apr 2013 15:48:34 +0000 (11:48 -0400)
commit491402a7876e91aa491c33f70ed4e86e59f06c8b
treef8357ff807c5a480aa677f6a0cfaced45d5fa765
parent9c6bdbb8dd58c8de8f36e1deb6b768918c85c249
nfsd: fix bug on nfs4 stateid deallocation

NFS4_OO_PURGE_CLOSE is not handled properly. To avoid memory leak, nfs4
stateid which is pointed by oo_last_closed_stid is freed in nfsd4_close(),
but NFS4_OO_PURGE_CLOSE isn't cleared meanwhile. So the stateid released in
THIS close procedure may be freed immediately in the coming encoding function.
Sorry that Signed-off-by was forgotten in last version.

Signed-off-by: Yanchuan Nian <ycnian@gmail.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c