diff options
author | Trond Myklebust <trond.myklebust@primarydata.com> | 2015-03-02 23:32:08 -0500 |
---|---|---|
committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2015-03-03 13:02:29 -0500 |
commit | 874f946376de57c8d6230b30ad71f742883fee3a (patch) | |
tree | 0fd166cc4798b50069d1120f822f094a60b7a9c2 /fs/Kconfig.binfmt | |
parent | ec3ca4e57e00d52ff724b0ae49f4489667a9c311 (diff) | |
download | op-kernel-dev-874f946376de57c8d6230b30ad71f742883fee3a.zip op-kernel-dev-874f946376de57c8d6230b30ad71f742883fee3a.tar.gz |
NFS: Fix a regression in the read() syscall
When invalidating the page cache for a regular file, we want to first
sync all dirty data to disk and then call invalidate_inode_pages2().
The latter relies on nfs_launder_page() and nfs_release_page() to deal
respectively with dirty pages, and unstable written pages.
When commit 9590544694bec ("NFS: avoid deadlocks with loop-back mounted
NFS filesystems.") changed the behaviour of nfs_release_page(), then it
made it possible for invalidate_inode_pages2() to fail with an EBUSY.
Unfortunately, that error is then propagated back to read().
Let's therefore work around the problem for now by protecting the call
to sync the data and invalidate_inode_pages2() so that they are atomic
w.r.t. the addition of new writes.
Later on, we can revisit whether or not we still need nfs_launder_page()
and nfs_release_page().
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/Kconfig.binfmt')
0 files changed, 0 insertions, 0 deletions