| commit | a1643a92f6de92074116922a2d2906dd33499ff4 | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | Sat Sep 29 17:25:43 2007 -0400 |
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | Tue Oct 09 17:19:48 2007 -0400 |
| tree | 9047e929e13d48b53a8d3512ce31ac9ab6b1832d | |
| parent | 3258b4fa552c4f994b5e6490a8ad88f5d7e0e648 [diff] |
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>