diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-09-29 21:25:43 (GMT) |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-10-09 21:19:48 (GMT) |
| commit | a1643a92f6de92074116922a2d2906dd33499ff4 (patch) | |
| tree | 9047e929e13d48b53a8d3512ce31ac9ab6b1832d /fs/nfs | |
| parent | 3258b4fa552c4f994b5e6490a8ad88f5d7e0e648 (diff) | |
| download | linux-a1643a92f6de92074116922a2d2906dd33499ff4.tar.xz | |
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 'fs/nfs')
| -rw-r--r-- | fs/nfs/dir.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c index 35b447d..a03ed2f 100644 --- a/fs/nfs/dir.c +++ b/fs/nfs/dir.c @@ -788,7 +788,7 @@ static int nfs_lookup_revalidate(struct dentry * dentry, struct nameidata *nd) out_zap_parent: nfs_zap_caches(dir); out_bad: - NFS_CACHEINV(dir); + nfs_mark_for_revalidate(dir); if (inode && S_ISDIR(inode->i_mode)) { /* Purge readdir caches. */ nfs_zap_caches(inode); |