summaryrefslogtreecommitdiff
path: root/fs/nfs/symlink.c
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@primarydata.com>2014-06-20 21:11:01 +0400
committerTrond Myklebust <trond.myklebust@primarydata.com>2014-06-25 02:46:57 +0400
commit6edf96097b1df34fcd332f7ee4ba120fbc1d16c3 (patch)
tree86dc9b545453c505149cc7adbe4f1eac3e5338d2 /fs/nfs/symlink.c
parentf2467b6f64da7d8446211c21f6fcd8fa10e8d948 (diff)
downloadlinux-6edf96097b1df34fcd332f7ee4ba120fbc1d16c3.tar.xz
NFS: Don't mark the data cache as invalid if it has been flushed
Now that we have functions such as nfs_write_pageuptodate() that use the cache_validity flags to check if the data cache is valid or not, it is a little more important to keep the flags in sync with the state of the data cache. In particular, we'd like to ensure that if the data cache is empty, we don't start marking it as needing revalidation. Reported-by: Scott Mayhew <smayhew@redhat.com> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/nfs/symlink.c')
0 files changed, 0 insertions, 0 deletions