Jeff Layton 37cbe5b6d1 nfsd: don't return an unhashed lock stateid after taking mutex ... commit dd257933fa4b9fea66a1195f8a15111029810abc upstream. nfsd4_lock will take the st_mutex before working with the stateid it gets, but between the time when we drop the cl_lock and take the mutex, the stateid could become unhashed (a'la FREE_STATEID). If that happens the lock stateid returned to the client will be forgotten. Fix this by first moving the st_mutex acquisition into lookup_or_create_lock_state. Then, have it check to see if the lock stateid is still hashed after taking the mutex. If it's not, then put the stateid and try the find/create again. Signed-off-by: Jeff Layton <jlayton@redhat.com> Tested-by: Alexey Kodanev <alexey.kodanev@oracle.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2016-08-20 18:09:21 +02:00
..
acl.h
auth.c
auth.h
blocklayout.c
blocklayoutxdr.c
blocklayoutxdr.h
cache.h
current_stateid.h
export.c
export.h
fault_inject.c
idmap.h
Kconfig
lockd.c
Makefile
netns.h
nfs2acl.c	nfsd: check permissions when setting ACLs	2016-07-27 09:47:30 -07:00
nfs3acl.c	nfsd: check permissions when setting ACLs	2016-07-27 09:47:30 -07:00
nfs3proc.c
nfs3xdr.c
nfs4acl.c	nfsd: check permissions when setting ACLs	2016-07-27 09:47:30 -07:00
nfs4callback.c	nfsd4/rpc: move backchannel create logic into rpc code	2016-07-27 09:47:30 -07:00
nfs4idmap.c
nfs4layouts.c
nfs4proc.c
nfs4recover.c
nfs4state.c	nfsd: don't return an unhashed lock stateid after taking mutex	2016-08-20 18:09:21 +02:00
nfs4xdr.c
nfscache.c
nfsctl.c
nfsd.h
nfsfh.c
nfsfh.h
nfsproc.c
nfssvc.c
nfsxdr.c
pnfs.h
state.h	nfsd: Always lock state exclusively.	2016-07-27 09:47:30 -07:00
stats.c
stats.h
trace.c
trace.h
vfs.c
vfs.h
xdr.h
xdr3.h
xdr4.h
xdr4cb.h