summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2007-09-29 23:25:43 +0200
committerTrond Myklebust <Trond.Myklebust@netapp.com>2007-10-09 23:19:48 +0200
commita1643a92f6de92074116922a2d2906dd33499ff4 (patch)
tree9047e929e13d48b53a8d3512ce31ac9ab6b1832d /block
parentNFS: Remove bogus nfs_mark_for_revalidate() in nfs_lookup (diff)
downloadlinux-a1643a92f6de92074116922a2d2906dd33499ff4.tar.xz
linux-a1643a92f6de92074116922a2d2906dd33499ff4.zip
NFS: NFS_CACHEINV() should not test for nfs_caches_unstable()
The fact that we're in the process of modifying the inode does not mean that we should not invalidate the attribute and data caches. The defensive thing is to always invalidate when we're confronted with inode mtime/ctime or change_attribute updates that we do not immediately recognise. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions