]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
btrfs: reset block group chunk force if we have to wait
authorJosef Bacik <josef@toxicpanda.com>
Mon, 13 Jun 2022 22:31:17 +0000 (18:31 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 17 Aug 2022 12:42:25 +0000 (14:42 +0200)
commit21d435d3a72ea3a5f5c809cbe9b97837c8f38b69
tree7aaaa932adbe8efd47b6327f4d131ab3a1d481be
parentfeb8322821830485d2b4fc426f17ed1c41377a64
btrfs: reset block group chunk force if we have to wait

[ Upstream commit 1314ca78b2c35d3e7d0f097268a2ee6dc0d369ef ]

If you try to force a chunk allocation, but you race with another chunk
allocation, you will end up waiting on the chunk allocation that just
occurred and then allocate another chunk.  If you have many threads all
doing this at once you can way over-allocate chunks.

Fix this by resetting force to NO_FORCE, that way if we think we need to
allocate we can, otherwise we don't force another chunk allocation if
one is already happening.

Reviewed-by: Filipe Manana <fdmanana@suse.com>
CC: stable@vger.kernel.org # 5.4+
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/btrfs/block-group.c