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
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 737 bytes |
| Makefile | -rw-r--r-- | 325 bytes |
| coherent.c | -rw-r--r-- | 11.0 KB |
| contiguous.c | -rw-r--r-- | 7.9 KB |
| debug.c | -rw-r--r-- | 46.0 KB |
| direct.c | -rw-r--r-- | 9.5 KB |
| mapping.c | -rw-r--r-- | 8.2 KB |
| swiotlb.c | -rw-r--r-- | 24.0 KB |
| virt.c | -rw-r--r-- | 1.4 KB |
Computing file changes ...
