LU-3651 mdt: upgrade 2.4.53 to 2.5.53 for rename lock

Since cross-MDT rename will be supported in 2.6, so change
VERSION from 2.4.53 to 2.5.53 in mdt_rename_lock, until then
each MDT still use local rename lock to protect rename process.

Signed-off-by: wang di <di.wang@intel.com>
Change-Id: I4b4e66bc3879cd0f6ad768ef01d388dfe004ee94
Reviewed-on: http://review.whamcloud.com/7151
Tested-by: Hudson
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Tested-by: Maloo <whamcloud.maloo@gmail.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>

diff --git a/lustre/mdt/mdt_reint.c b/lustre/mdt/mdt_reint.c
index c861792..2a0aa4e 100644 (file)
--- a/lustre/mdt/mdt_reint.c
+++ b/lustre/mdt/mdt_reint.c
@@ -1034,7 +1034,7 @@ static int mdt_rename_lock(struct mdt_thread_info *info,
 
        memset(policy, 0, sizeof *policy);
        policy->l_inodebits.bits = MDS_INODELOCK_UPDATE;
-#if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 4, 53, 0)
+#if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 5, 53, 0)
        /* In phase I, we will not do cross-rename, so local BFL lock would
         * be enough
         */