summaryrefslogtreecommitdiffstats
path: root/Kbuild
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2022-03-07 10:41:44 +1100
committerTrond Myklebust <trond.myklebust@hammerspace.com>2022-03-13 12:59:35 -0400
commitc265de257f558a05c1859ee9e3fed04883b9ec0e (patch)
tree3f1f684db4b2c37bbdcdf9f82a232fe33cacfc85 /Kbuild
parent64158668ac8b31626a8ce48db4cad08496eb8340 (diff)
downloadlinux-stable-c265de257f558a05c1859ee9e3fed04883b9ec0e.tar.gz
linux-stable-c265de257f558a05c1859ee9e3fed04883b9ec0e.tar.bz2
linux-stable-c265de257f558a05c1859ee9e3fed04883b9ec0e.zip
NFS: swap-out must always use STABLE writes.
The commit handling code is not safe against memory-pressure deadlocks when writing to swap. In particular, nfs_commitdata_alloc() blocks indefinitely waiting for memory, and this can consume all available workqueue threads. swap-out most likely uses STABLE writes anyway as COND_STABLE indicates that a stable write should be used if the write fits in a single request, and it normally does. However if we ever swap with a small wsize, or gather unusually large numbers of pages for a single write, this might change. For safety, make it explicit in the code that direct writes used for swap must always use FLUSH_STABLE. Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions