NFS: Don't abuse NFS_INO_REVAL_FORCED in nfs_post_op_update_inode_locked()

The NFS_INO_REVAL_FORCED flag now really only has meaning for the
case when we've just been handed a delegation for a file that was already
cached, and we're unsure about that cache.

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>

1 files changed, 0 insertions, 7 deletions

diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index a0cd79646c1b..5561d78b7998 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -1550,13 +1550,6 @@ static int nfs_post_op_update_inode_locked(struct inode *inode, struct nfs_fattr
 {
         unsigned long invalid = NFS_INO_INVALID_ATTR;
 
-        /*
-         * Don't revalidate the pagecache if we hold a delegation, but do
-         * force an attribute update
-         */
-        if (NFS_PROTO(inode)->have_delegation(inode, FMODE_READ))
-                invalid = NFS_INO_INVALID_ATTR|NFS_INO_REVAL_FORCED;
-
         if (S_ISDIR(inode->i_mode))
                 invalid |= NFS_INO_INVALID_DATA;
         nfs_set_cache_invalid(inode, invalid);