From ccfeb506231348a3c60ab0fdb5753a574653e3c0 Mon Sep 17 00:00:00 2001 From: Trond Myklebust Date: Sat, 13 Jan 2007 02:28:12 -0500 Subject: NFS: Fix up "rm -rf"... When a file is being scheduled for deletion by means of the sillyrename mechanism, it makes sense to start out writeback of the dirty data as soon as possible in order to ensure that the delete can occur. Examples of cases where this is an issue include "rm -rf", which will busy-wait until the file is closed, and the sillyrename completes. Signed-off-by: Trond Myklebust --- fs/nfs/dir.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'fs/nfs/dir.c') diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c index d9ba8cb0ee7..bd269d26882 100644 --- a/fs/nfs/dir.c +++ b/fs/nfs/dir.c @@ -1443,6 +1443,8 @@ static int nfs_unlink(struct inode *dir, struct dentry *dentry) if (atomic_read(&dentry->d_count) > 1) { spin_unlock(&dentry->d_lock); spin_unlock(&dcache_lock); + /* Start asynchronous writeout of the inode */ + write_inode_now(dentry->d_inode, 0); error = nfs_sillyrename(dir, dentry); unlock_kernel(); return error; -- cgit v1.2.3-18-g5258