aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/gcc-plugins/randomize_layout_plugin.c
diff options
context:
space:
mode:
authorTrond Myklebust <[email protected]>2018-03-07 20:22:31 +0000
committerTrond Myklebust <[email protected]>2018-03-08 17:56:32 +0000
commitc4f24df942a181699c5bab01b8e5e82b925f77f3 (patch)
tree8ee1067aaac971f1de07c609dc17f2fa03a3b69c /scripts/gcc-plugins/randomize_layout_plugin.c
parentpNFS: Prevent the layout header refcount going to zero in pnfs_roc() (diff)
downloadkernel-c4f24df942a181699c5bab01b8e5e82b925f77f3.tar.gz
kernel-c4f24df942a181699c5bab01b8e5e82b925f77f3.zip
NFS: Fix unstable write completion
We do want to respect the FLUSH_SYNC argument to nfs_commit_inode() to ensure that all outstanding COMMIT requests to the inode in question are complete. Currently we may exit early from both nfs_commit_inode() and nfs_write_inode() even if there are COMMIT requests in flight, or unstable writes on the commit list. In order to get the right semantics w.r.t. sync_inode(), we don't need to have nfs_commit_inode() reset the inode dirty flags when called from nfs_wb_page() and/or nfs_wb_all(). We just need to ensure that nfs_write_inode() leaves them in the right state if there are outstanding commits, or stable pages. Reported-by: Scott Mayhew <[email protected]> Fixes: dc4fd9ab01ab ("nfs: don't wait on commit in nfs_commit_inode()...") Cc: [email protected] # v4.14+ Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/randomize_layout_plugin.c')
0 files changed, 0 insertions, 0 deletions