NFS: Use nfs_refresh_inode() in ops that aren't expected to change the inode

nfs_post_op_update_inode() is really only meant to be used if we expect the
inode and its attributes to have changed in some way.

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

1 files changed, 2 insertions, 3 deletions

diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 52af5a7d679e..30d5dd5735cd 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -2475,8 +2475,7 @@ static int nfs4_commit_done(struct rpc_task *task, struct nfs_write_data *data)
                 rpc_restart_call(task);
                 return -EAGAIN;
         }
-        if (task->tk_status >= 0)
-                nfs_post_op_update_inode(inode, data->res.fattr);
+        nfs_refresh_inode(inode, data->res.fattr);
         return 0;
 }
 
@@ -3046,7 +3045,7 @@ static int _nfs4_proc_delegreturn(struct inode *inode, struct rpc_cred *cred, co
         if (status == 0) {
                 status = data->rpc_status;
                 if (status == 0)
-                        nfs_post_op_update_inode(inode, &data->fattr);
+                        nfs_refresh_inode(inode, &data->fattr);
         }
         rpc_put_task(task);
         return status;