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-- 1013 bytes
Makefile -rw-r--r-- 98 bytes
dir.c -rw-r--r-- 4.1 KB
file.c -rw-r--r-- 13.5 KB
group.c -rw-r--r-- 11.4 KB
mount.c -rw-r--r-- 1.7 KB
symlink.c -rw-r--r-- 4.8 KB
sysfs.h -rw-r--r-- 844 bytes

back to top