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-- | 1.2 KB |
| Makefile | -rw-r--r-- | 173 bytes |
| autofs_i.h | -rw-r--r-- | 7.4 KB |
| dev-ioctl.c | -rw-r--r-- | 17.8 KB |
| expire.c | -rw-r--r-- | 15.3 KB |
| init.c | -rw-r--r-- | 1.1 KB |
| inode.c | -rw-r--r-- | 8.4 KB |
| root.c | -rw-r--r-- | 24.4 KB |
| symlink.c | -rw-r--r-- | 790 bytes |
| waitq.c | -rw-r--r-- | 13.4 KB |
Computing file changes ...
