Btrfs: remove unnecessary inode generation lookup in send
authorFilipe Manana <fdmanana@gmail.com>
Tue, 18 Mar 2014 17:56:06 +0000 (17:56 +0000)
committerChris Mason <clm@fb.com>
Fri, 21 Mar 2014 00:15:28 +0000 (17:15 -0700)
No need to search in the send tree for the generation number of the inode,
we already have it in the recorded_ref structure passed to us.

Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: Chris Mason <clm@fb.com>
fs/btrfs/send.c

index 6463691796974ad5f9951bbcfd722296a9014845..92d4ae8a8ae66f431d2d20a71ac26f6880b8a849 100644 (file)
@@ -3179,7 +3179,7 @@ static int wait_for_parent_move(struct send_ctx *sctx,
        int ret;
        u64 ino = parent_ref->dir;
        u64 parent_ino_before, parent_ino_after;
-       u64 new_gen, old_gen;
+       u64 old_gen;
        struct fs_path *path_before = NULL;
        struct fs_path *path_after = NULL;
        int len1, len2;
@@ -3197,12 +3197,7 @@ static int wait_for_parent_move(struct send_ctx *sctx,
        else if (ret < 0)
                return ret;
 
-       ret = get_inode_info(sctx->send_root, ino, NULL, &new_gen,
-                            NULL, NULL, NULL, NULL);
-       if (ret < 0)
-               return ret;
-
-       if (new_gen != old_gen)
+       if (parent_ref->dir_gen != old_gen)
                return 0;
 
        path_before = fs_path_alloc();