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 |
|---|---|---|
| Makefile | -rw-r--r-- | 272 bytes |
| cgroup-internal.h | -rw-r--r-- | 7.9 KB |
| cgroup-v1.c | -rw-r--r-- | 33.8 KB |
| cgroup.c | -rw-r--r-- | 158.6 KB |
| cpuset.c | -rw-r--r-- | 76.3 KB |
| debug.c | -rw-r--r-- | 8.3 KB |
| freezer.c | -rw-r--r-- | 12.4 KB |
| namespace.c | -rw-r--r-- | 3.3 KB |
| pids.c | -rw-r--r-- | 8.9 KB |
| rdma.c | -rw-r--r-- | 14.9 KB |
| rstat.c | -rw-r--r-- | 10.8 KB |
Computing file changes ...
