summaryrefslogtreecommitdiffstats
path: root/fs/nfs
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2010-07-31 14:29:06 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2010-08-03 22:06:41 -0400
commit0a8ebba943dd89bdd57c5dab5a66932f690847d9 (patch)
treeb7ef484c9ecb62ebae09c6739fe016d9954cf243 /fs/nfs
parent1b924e5f878e3cd62a20bd8dbf3b911a40185a99 (diff)
downloadop-kernel-dev-0a8ebba943dd89bdd57c5dab5a66932f690847d9.zip
op-kernel-dev-0a8ebba943dd89bdd57c5dab5a66932f690847d9.tar.gz
NFS: nfs_rename() should not have to flush out writebacks
We don't really support nfs servers that invalidate the file handle after a rename, so precautions such as flushing out dirty data before renaming the file are superfluous. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs')
-rw-r--r--fs/nfs/dir.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
index 782b431..067a051 100644
--- a/fs/nfs/dir.c
+++ b/fs/nfs/dir.c
@@ -1652,16 +1652,7 @@ static int nfs_rename(struct inode *old_dir, struct dentry *old_dentry,
}
}
- /*
- * ... prune child dentries and writebacks if needed.
- */
- if (atomic_read(&old_dentry->d_count) > 1) {
- if (S_ISREG(old_inode->i_mode))
- nfs_wb_all(old_inode);
- shrink_dcache_parent(old_dentry);
- }
nfs_inode_return_delegation(old_inode);
-
if (new_inode != NULL)
nfs_inode_return_delegation(new_inode);
OpenPOWER on IntegriCloud