diff options
author | Josef Bacik <josef@toxicpanda.com> | 2018-10-11 22:54:03 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2018-10-19 13:20:03 +0300 |
commit | 21a94f7acf0f748599ea552af5d9ee7d7e41c72f (patch) | |
tree | b43ed6c451e463f5e93bc47e50e3bde7c194a475 /crypto/cts.c | |
parent | b2b5b6502c3ddc448be825974036ef4d8966e888 (diff) | |
download | linux-21a94f7acf0f748599ea552af5d9ee7d7e41c72f.tar.xz |
btrfs: reset max_extent_size properly
If we use up our block group before allocating a new one we'll easily
get a max_extent_size that's set really really low, which will result in
a lot of fragmentation. We need to make sure we're resetting the
max_extent_size when we add a new chunk or add new space.
CC: stable@vger.kernel.org # 4.4+
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'crypto/cts.c')
0 files changed, 0 insertions, 0 deletions