From: Alexandre Oliva <lxoliva@fsfla.org>
Date: Mon, 28 Nov 2011 14:36:17 +0000 (-0200)
Subject: Btrfs: don't set up allocation result twice
X-Git-Tag: v3.3-rc1~26^2~13^2~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fc7c1077ceb99c35e5f9d0ce03dc7740565bb2bf;p=profile%2Fivi%2Fkernel-x86-ivi.git

Btrfs: don't set up allocation result twice

We store the allocation start and length twice in ins, once right
after the other, but with intervening calls that may prevent the
duplicate from being optimized out by the compiler.  Remove one of the
assignments.

Signed-off-by: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
---

diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 5ea3acc..37594e4 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -5441,9 +5441,6 @@ checks:
 			goto loop;
 		}
 
-		ins->objectid = search_start;
-		ins->offset = num_bytes;
-
 		if (offset < search_start)
 			btrfs_add_free_space(used_block_group, offset,
 					     search_start - offset);