NFS: Don't force a dcache revalidation if nfs_wcc_update_inode succeeds

Browse source

The reason is that if the weak cache consistency update was successful,
then we know that our client must be the only one that changed the
directory, and we've already updated the dcache to reflect the change.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

...

This commit is contained in:

Trond Myklebust 2007-09-27 10:07:31 -04:00

parent e323ea46d9

commit 17cadc9537

3 changed files with 11 additions and 11 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

11

fs/nfs/inode.c

View file

7

fs/nfs/nfs4proc.c

View file

4

include/linux/nfs_fs.h

View file