From: Siddharth Mishra <smish149@asu.edu>
To: dsterba@suse.com
Cc: mason@kernel.org, josef@toxicpanda.com, wqu@suse.com,
fdmanana@kernel.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, Siddharth Mishra <smish149@asu.edu>,
syzbot+dc9291cf132691aeb478@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: [PATCH 1/2] btrfs: overwrite a leftover balance item instead of BUG_ON()
Date: Thu, 5 Nov 2026 14:47:37 -0700 [thread overview]
Message-ID: <20261105214738.111967-2-smish149@asu.edu> (raw)
In-Reply-To: <20261105214738.111967-1-smish149@asu.edu>
[BUG]
A balance ioctl can hit this BUG_ON():
kernel BUG at fs/btrfs/volumes.c:5088!
Oops: invalid opcode: 0000 [#1] SMP NOPTI
RIP: 0010:btrfs_balance (fs/btrfs/volumes.c:5088)
Call Trace:
<TASK>
btrfs_ioctl (fs/btrfs/ioctl.c:3523 fs/btrfs/ioctl.c:5650)
__x64_sys_ioctl
do_syscall_64
entry_SYSCALL_64_after_hwframe
</TASK>
[CAUSE]
btrfs_balance() expects insert_balance_item() to return -EEXIST only
when a balance item is on disk, and a balance item to be on disk only
when fs_info->balance_ctl is set (a paused balance, or one recovered
at mount). So for a new balance it uses BUG_ON(ret == -EEXIST).
Both assumptions can be wrong:
- insert_balance_item() inserts the item, then commits the transaction.
btrfs_commit_transaction() can fail without aborting the
transaction, for example when btrfs_start_dirty_block_groups() fails
to allocate a path. Then balance fails with -ENOMEM and
balance_ctl is freed, but the item stays in the running transaction.
The next balance ioctl finds the item and gets -EEXIST.
- When the transaction was aborted with -EEXIST, for example after
"failed to run delayed ref ... -17" on a corrupted extent tree,
btrfs_commit_transaction() returns the abort error, -EEXIST, and
there is no balance item at all.
[FIX]
Mount turns any balance item on disk into a paused balance, so a new
balance can only find an item left by a balance of the same mount that
failed after inserting it. No balance owns that item, so let a new
balance overwrite it, run, and delete it at the end as usual, as Filipe
suggested in [1].
For a resumed balance -EEXIST is the normal result. Any other error,
including the -EEXIST of an aborted transaction for a new balance, now
goes to the existing error path.
The BUG_ON() checks on the return value go away, and the one on
fs_info->balance_ctl becomes an ASSERT().
Reported-by: syzbot+dc9291cf132691aeb478@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=dc9291cf132691aeb478
Link: https://lore.kernel.org/linux-btrfs/ZNzE6CFOzu9kDG+G@debian0.Home/ [1]
Fixes: 1bbc621ef284 ("Btrfs: allow block group cache writeout outside critical section in commit")
Cc: stable@vger.kernel.org # 4.1+
Suggested-by: Filipe Manana <fdmanana@kernel.org>
Signed-off-by: Siddharth Mishra <smish149@asu.edu>
---
fs/btrfs/volumes.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 3d4ef6725..4a8e5078b 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -3998,6 +3998,8 @@ static int insert_balance_item(struct btrfs_fs_info *fs_info,
ret = btrfs_insert_empty_item(trans, root, path, &key,
sizeof(*item));
+ if (ret == -EEXIST && !(bctl->flags & BTRFS_BALANCE_RESUME))
+ ret = 0;
if (ret)
goto out;
@@ -5081,17 +5083,17 @@ int btrfs_balance(struct btrfs_fs_info *fs_info,
}
ret = insert_balance_item(fs_info, bctl);
- if (ret && ret != -EEXIST)
+ if (ret == -EEXIST && (bctl->flags & BTRFS_BALANCE_RESUME))
+ ret = 0;
+ if (ret)
goto out;
if (!(bctl->flags & BTRFS_BALANCE_RESUME)) {
- BUG_ON(ret == -EEXIST);
- BUG_ON(fs_info->balance_ctl);
+ ASSERT(!fs_info->balance_ctl);
spin_lock(&fs_info->balance_lock);
fs_info->balance_ctl = bctl;
spin_unlock(&fs_info->balance_lock);
} else {
- BUG_ON(ret != -EEXIST);
spin_lock(&fs_info->balance_lock);
update_balance_args(bctl);
spin_unlock(&fs_info->balance_lock);
--
2.54.0
next prev parent reply other threads:[~2026-11-05 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 21:47 [PATCH 0/2] btrfs: balance item fixes Siddharth Mishra
2026-11-05 21:47 ` Siddharth Mishra [this message]
2026-11-05 22:09 ` [PATCH 1/2] btrfs: overwrite a leftover balance item instead of BUG_ON() Qu Wenruo
2026-11-05 22:40 ` Siddharth Mishra
2026-11-05 22:43 ` Qu Wenruo
2026-11-05 21:47 ` [PATCH 2/2] btrfs: tree-checker: add balance item size check Siddharth Mishra
2026-11-05 22:06 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261105214738.111967-2-smish149@asu.edu \
--to=smish149@asu.edu \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+dc9291cf132691aeb478@syzkaller.appspotmail.com \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®