btrfs: don't use ctl->free_space for max_extent_size
authorJosef Bacik <jbacik@fb.com>
Thu, 11 Oct 2018 19:54:09 +0000 (15:54 -0400)
committerDavid Sterba <dsterba@suse.com>
Fri, 19 Oct 2018 10:20:03 +0000 (12:20 +0200)
commitfb5c39d7a887108087de6ff93d3f326b01b4ef41
tree5f37db86a709d30c3ef123b6393d132c2bf1f299
parentad22cf6ea47fa20fbe11ac324a0a15c0a9a4a2a9
btrfs: don't use ctl->free_space for max_extent_size

max_extent_size is supposed to be the largest contiguous range for the
space info, and ctl->free_space is the total free space in the block
group.  We need to keep track of these separately and _only_ use the
max_free_space if we don't have a max_extent_size, as that means our
original request was too large to search any of the block groups for and
therefore wouldn't have a max_extent_size set.

CC: stable@vger.kernel.org # 4.14+
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Josef Bacik <jbacik@fb.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent-tree.c