btrfs: use reada direction enum instead of constant value in load_free_space_tree
authorGu JinXiang <gujx@cn.fujitsu.com>
Thu, 11 Jan 2018 08:12:18 +0000 (16:12 +0800)
committerDavid Sterba <dsterba@suse.com>
Mon, 26 Mar 2018 13:09:37 +0000 (15:09 +0200)
commit7ce311d552e473a5176f8bb143fb45de64b8bd81
tree7df2369c78433bb0668026f9088016c4869bc322
parent019599ada73ce8ac0b0d60705819eba95df54630
btrfs: use reada direction enum instead of constant value in load_free_space_tree

load_free_space_tree calls either function load_free_space_bitmaps or
load_free_space_extents. And either of those two will lead to call
btrfs_next_item.  So in function load_free_space_tree, use READA_FORWARD
to read forward ahead.

This also changes the value from READA_BACK to READA_FORWARD, since
according to the logic, it should reada_for_search forward, not
backward.

Signed-off-by: Gu JinXiang <gujx@cn.fujitsu.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
[ update changelog ]
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/free-space-tree.c