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-- | 10.1 KB |
| Makefile | -rw-r--r-- | 507 bytes |
| autosleep.c | -rw-r--r-- | 2.6 KB |
| console.c | -rw-r--r-- | 3.5 KB |
| hibernate.c | -rw-r--r-- | 28.5 KB |
| main.c | -rw-r--r-- | 19.1 KB |
| power.h | -rw-r--r-- | 8.7 KB |
| poweroff.c | -rw-r--r-- | 990 bytes |
| process.c | -rw-r--r-- | 5.6 KB |
| qos.c | -rw-r--r-- | 19.1 KB |
| snapshot.c | -rw-r--r-- | 71.6 KB |
| suspend.c | -rw-r--r-- | 15.2 KB |
| suspend_test.c | -rw-r--r-- | 5.7 KB |
| swap.c | -rw-r--r-- | 37.6 KB |
| user.c | -rw-r--r-- | 10.2 KB |
| wakelock.c | -rw-r--r-- | 5.8 KB |
Computing file changes ...
