summaryrefslogtreecommitdiffstats
path: root/fs/jbd2/commit.c
diff options
context:
space:
mode:
authorHolger Hoffstätte <holger.hoffstaette@googlemail.com>2015-11-17 12:29:32 +0100
committerChris Mason <clm@fb.com>2015-11-25 14:27:33 +0100
commitdba72cb30b6a4811038128c8a98b268d18ca60fe (patch)
treecde1595891c3167cd7da675cd8519df80ac7016e /fs/jbd2/commit.c
parentbtrfs: qgroup: account shared subtree during snapshot delete (diff)
downloadlinux-dba72cb30b6a4811038128c8a98b268d18ca60fe.tar.xz
linux-dba72cb30b6a4811038128c8a98b268d18ca60fe.zip
btrfs: fix balance range usage filters in 4.4-rc
There's a regression in 4.4-rc since commit bc3094673f22 (btrfs: extend balance filter usage to take minimum and maximum) in that existing (non-ranged) balance with -dusage=x no longer works; all chunks are skipped. After staring at the code for a while and wondering why a non-ranged balance would even need min and max thresholds (..which then were not set correctly, leading to the bug) I realized that the only problem was the fact that the filter functions were named wrong, thanks to patching copypasta. Simply renaming both functions lets the existing btrfs-progs call balance with -dusage=x and now the non-ranged filter function is invoked, properly using only a single chunk limit. Signed-off-by: Holger Hoffstätte <holger.hoffstaette@googlemail.com> Fixes: bc3094673f22 ("btrfs: extend balance filter usage to take minimum and maximum") Reviewed-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions