Trond Myklebust 7111dc7392 NFSv4: Fix an infinite looping problem with the nfs4_state_manager ... Commit 76db6d9500 (nfs41: add session setup to the state manager) introduces an infinite loop possibility in the NFSv4 state manager. By first checking nfs4_has_session() before clearing the NFS4CLNT_SESSION_SETUP flag, it allows for a situation where someone sets that flag, but it never gets cleared, and so the state manager loops. In fact commit c3fad1b1aa (nfs41: add session reset to state manager) causes this to happen every time we get a network partition error. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Tested-by: Daniel J Blueman <daniel.blueman@gmail.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2009-08-24 16:28:42 -07:00
..
callback_proc.c
callback_xdr.c
callback.c
callback.h
client.c
delegation.c
delegation.h
dir.c
direct.c
file.c
fscache-index.c
fscache.c
fscache.h
getroot.c
idmap.c
inode.c
internal.h
iostat.h
Kconfig
Makefile
mount_clnt.c
namespace.c
nfs2xdr.c
nfs3acl.c
nfs3proc.c
nfs3xdr.c
nfs4_fs.h
nfs4namespace.c
nfs4proc.c
nfs4renewd.c
nfs4state.c
nfs4xdr.c
nfsroot.c
pagelist.c
proc.c
read.c
super.c
symlink.c
sysctl.c
unlink.c
write.c