aboutsummaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent_io.c
diff options
context:
space:
mode:
authorLiu Bo <liubo2009@cn.fujitsu.com>2012-02-16 05:34:36 -0500
committerDavid Sterba <dsterba@suse.cz>2012-02-21 10:02:10 -0500
commit692e5759a43b916f0b66bcb39b2957499992381e (patch)
treeb3e1ea148b1702c63ccca95712d7cad2bb35a1ea /fs/btrfs/extent_io.c
parentd9b0218f6cb682aa6a4ada2bfc5a25fdf3018563 (diff)
Btrfs: be less strict on finding next node in clear_extent_bit
In clear_extent_bit, it is enough that next node is adjacent in tree level. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
Diffstat (limited to 'fs/btrfs/extent_io.c')
-rw-r--r--fs/btrfs/extent_io.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 37259ff5cd71..45ca8f9b0d61 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -582,8 +582,7 @@ next:
582 if (start <= end && next_node) { 582 if (start <= end && next_node) {
583 state = rb_entry(next_node, struct extent_state, 583 state = rb_entry(next_node, struct extent_state,
584 rb_node); 584 rb_node);
585 if (state->start == start) 585 goto hit_next;
586 goto hit_next;
587 } 586 }
588 goto search_again; 587 goto search_again;
589 588