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 |
---|---|---|
apparmor | ||
integrity | ||
keys | ||
loadpin | ||
selinux | ||
smack | ||
tomoyo | ||
yama | ||
Kconfig | -rw-r--r-- | 9.8 KB |
Makefile | -rw-r--r-- | 1.0 KB |
commoncap.c | -rw-r--r-- | 39.0 KB |
device_cgroup.c | -rw-r--r-- | 20.4 KB |
inode.c | -rw-r--r-- | 10.5 KB |
lsm_audit.c | -rw-r--r-- | 10.6 KB |
min_addr.c | -rw-r--r-- | 1.3 KB |
security.c | -rw-r--r-- | 45.3 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...