Jeff Layton dd257933fa nfsd: don't return an unhashed lock stateid after taking mutex ... 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> Cc: stable@vger.kernel.org # feb9dad5 nfsd: Always lock state exclusively. Cc: stable@vger.kernel.org Signed-off-by: J. Bruce Fields <bfields@redhat.com>		2016-08-12 16:10:25 -04:00
..
acl.h
auth.c
auth.h
blocklayout.c	Highlights:	2016-08-04 19:59:06 -04:00
blocklayoutxdr.c	Highlights:	2016-08-04 19:59:06 -04:00
blocklayoutxdr.h
cache.h
current_stateid.h
export.c
export.h
fault_inject.c
flexfilelayout.c
flexfilelayoutxdr.c
flexfilelayoutxdr.h
idmap.h
Kconfig
lockd.c
Makefile
netns.h
nfs2acl.c
nfs3acl.c
nfs3proc.c
nfs3xdr.c
nfs4acl.c
nfs4callback.c
nfs4idmap.c
nfs4layouts.c
nfs4proc.c	nfsd: drop unnecessary MAY_EXEC check from create	2016-08-04 17:11:52 -04:00
nfs4recover.c
nfs4state.c	nfsd: don't return an unhashed lock stateid after taking mutex	2016-08-12 16:10:25 -04:00
nfs4xdr.c
nfscache.c
nfsctl.c
nfsd.h
nfsfh.c	nfsd: check d_can_lookup in fh_verify of directories	2016-08-04 17:11:48 -04:00
nfsfh.h
nfsproc.c	nfsd: reorganize nfsd_create	2016-08-04 17:11:49 -04:00
nfssvc.c
nfsxdr.c
pnfs.h
state.h
stats.c
stats.h
trace.c
trace.h
vfs.c	nfsd: fix dentry refcounting on create	2016-08-11 11:42:08 -04:00
vfs.h	nfsd: reorganize nfsd_create	2016-08-04 17:11:49 -04:00
xdr3.h
xdr4.h
xdr4cb.h
xdr.h