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-- 2.0 KB
Makefile -rw-r--r-- 206 bytes
base.c -rw-r--r-- 3.9 KB
fs.c -rw-r--r-- 18.9 KB
gcc_3_4.c -rw-r--r-- 13.8 KB
gcc_4_7.c -rw-r--r-- 13.5 KB
gcov.h -rw-r--r-- 2.7 KB

back to top