diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-09-30 01:25:43 +0400 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-10-10 01:19:48 +0400 |
| commit | a1643a92f6de92074116922a2d2906dd33499ff4 (patch) | |
| tree | 9047e929e13d48b53a8d3512ce31ac9ab6b1832d /include/linux/nfs_fs.h | |
| 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 'include/linux/nfs_fs.h')
| -rw-r--r-- | include/linux/nfs_fs.h | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/include/linux/nfs_fs.h b/include/linux/nfs_fs.h index 35d61924e0b9..c947803a7ba4 100644 --- a/include/linux/nfs_fs.h +++ b/include/linux/nfs_fs.h @@ -240,12 +240,6 @@ static inline void nfs_mark_for_revalidate(struct inode *inode) spin_unlock(&inode->i_lock); } -static inline void NFS_CACHEINV(struct inode *inode) -{ - if (!nfs_caches_unstable(inode)) - nfs_mark_for_revalidate(inode); -} - static inline int nfs_server_capable(struct inode *inode, int cap) { return NFS_SERVER(inode)->caps & cap; |