Skip to main content

Browse the archive

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 
NFSv4: Don't exit the state manager without clearing NFS4CLNT_MANAGER_RUNNING
 
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
Raw File
nopm.config 
CONFIG_PM=n
CONFIG_SUSPEND=n
CONFIG_HIBERNATION=n

# Triggers PM on OMAP
CONFIG_CPU_IDLE=n

# Triggers enablement via hibernate callbacks
CONFIG_XEN=n

# ARM/ARM64 architectures that select PM unconditionally
CONFIG_ARCH_OMAP2PLUS_TYPICAL=n
CONFIG_ARCH_RENESAS=n
CONFIG_ARCH_TEGRA=n
CONFIG_ARCH_VEXPRESS=n
back to top