nfsd: don't allow CLOSE to proceed until refcount on stateid drops
authorJeff Layton <jlayton@primarydata.com>
Wed, 30 Jul 2014 01:34:33 +0000 (21:34 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Thu, 31 Jul 2014 18:20:23 +0000 (14:20 -0400)
commitb401be22b5cf059290ee98106bc780e087407d45
treed6ac12b735b44e47752c224ec82b00ddec6b7f5a
parentd3134b1049c3db8fdac0c6dc9430facf30015a15
nfsd: don't allow CLOSE to proceed until refcount on stateid drops

Once we remove client_mutex protection, it'll be possible to have an
in-flight operation using an openstateid when a CLOSE call comes in.
If that happens, we can't just put the sc_file reference and clear its
pointer without risking an oops.

Fix this by ensuring that v4.0 CLOSE operations wait for the refcount
to drop before proceeding to do so.

Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c