[PATCH] Allow file systems to manually d_move() inside of ->rename()

Some file systems want to manually d_move() the dentries involved in a
rename.  We can do this by making use of the FS_ODD_RENAME flag if we just
have nfs_rename() unconditionally do the d_move().  While there, we rename
the flag to be more descriptive.

OCFS2 uses this to protect that part of the rename operation with a cluster
lock.

Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>

1 files changed, 4 insertions, 3 deletions

diff --git a/include/linux/fs.h b/include/linux/fs.h
index 555bc195c420..1d3e601ece73 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -92,9 +92,10 @@ extern int dir_notify_enable;
 #define FS_REQUIRES_DEV 1 
 #define FS_BINARY_MOUNTDATA 2
 #define FS_REVAL_DOT    16384   /* Check the paths ".", ".." for staleness */
-#define FS_ODD_RENAME   32768   /* Temporary stuff; will go away as soon
-                                  * as nfs_rename() will be cleaned up
-                                  */
+#define FS_RENAME_DOES_D_MOVE   32768   /* FS will handle d_move()
+                                         * during rename() internally.
+                                         */
+
 /*
  * These are the fs-independent mount-flags: up to 32 flags are supported
  */