summaryrefslogtreecommitdiffstats
path: root/fs/nfsd/nfs4proc.c
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@hammerspace.com>2018-11-05 11:10:50 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-11-21 09:19:23 +0100
commitc355fb8d33e6f9223b158a3bb4b7c883bedc5531 (patch)
tree82850191b5b24d8fdfc04dbe3fa2f5a18ea7f7d7 /fs/nfsd/nfs4proc.c
parent03c91663c0935fd1c7df5539ff6df65db8f57278 (diff)
downloadlinux-stable-c355fb8d33e6f9223b158a3bb4b7c883bedc5531.tar.gz
linux-stable-c355fb8d33e6f9223b158a3bb4b7c883bedc5531.tar.bz2
linux-stable-c355fb8d33e6f9223b158a3bb4b7c883bedc5531.zip
NFSv4: Don't exit the state manager without clearing NFS4CLNT_MANAGER_RUNNING
commit 21a446cf186570168b7281b154b1993968598aca upstream. 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+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/nfsd/nfs4proc.c')
0 files changed, 0 insertions, 0 deletions