Revision 21a446cf186570168b7281b154b1993968598aca authored by Trond Myklebust on 05 November 2018, 16:10:50 UTC, committed by Trond Myklebust on 12 November 2018, 21:39:13 UTC
If we exit the NFSv4 state manager due to a umount, then we can end up
leaving the NFS4CLNT_MANAGER_RUNNING flag set. If another mount causes
the nfs4_client to be rereferenced before it is destroyed, then we end
up never being able to recover state.

Fixes: 47c2199b6eb5 ("NFSv4.1: Ensure state manager thread dies on last ...")
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: stable@vger.kernel.org # v4.15+
1 parent ccda4af
History
File Mode Size
Kconfig -rw-r--r-- 1.2 KB
Makefile -rw-r--r-- 182 bytes
vxfs.h -rw-r--r-- 9.6 KB
vxfs_bmap.c -rw-r--r-- 7.8 KB
vxfs_dir.h -rw-r--r-- 3.2 KB
vxfs_extern.h -rw-r--r-- 2.7 KB
vxfs_fshead.c -rw-r--r-- 5.2 KB
vxfs_fshead.h -rw-r--r-- 2.5 KB
vxfs_immed.c -rw-r--r-- 2.6 KB
vxfs_inode.c -rw-r--r-- 9.2 KB
vxfs_inode.h -rw-r--r-- 5.7 KB
vxfs_lookup.c -rw-r--r-- 7.2 KB
vxfs_olt.c -rw-r--r-- 3.8 KB
vxfs_olt.h -rw-r--r-- 4.3 KB
vxfs_subr.c -rw-r--r-- 4.5 KB
vxfs_super.c -rw-r--r-- 8.8 KB

back to top