[v5.15] WARNING in btrfs_create_pending_block_groups

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f67653019430 Linux 5.15.118
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=152f25a8a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=717fa62bb7f0fe9
dashboard link: https://syzkaller.appspot.com/bug?extid=ecef109a157e70c06e25
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1012fabd280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1373c848a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d21188fbe046/disk-f6765301.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0c688e23e63/vmlinux-f6765301.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eca85b3bf72c/bzImage-f6765301.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a8f1311bb048/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ecef10...@syzkaller.appspotmail.com

BTRFS info (device loop0): doing ref verification
BTRFS info (device loop0): using free space tree
BTRFS info (device loop0): has skinny extents
BTRFS info (device loop0): enabling ssd optimizations
BTRFS info (device loop0): balance: start -f -susage=6,vrange=0..9223372036854775809
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3498 at fs/btrfs/block-group.c:2387 btrfs_create_pending_block_groups+0xe8b/0x1130 fs/btrfs/block-group.c:2387
Modules linked in:
CPU: 0 PID: 3498 Comm: syz-executor297 Not tainted 5.15.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:btrfs_create_pending_block_groups+0xe8b/0x1130 fs/btrfs/block-group.c:2387
Code: 3b f3 fe fd eb 26 e8 34 f3 fe fd 0f 1f 44 00 00 e8 2a f3 fe fd eb 48 e8 23 f3 fe fd 48 c7 c7 40 89 cb 8a 89 de e8 85 c5 ca fd <0f> 0b 48 8b 7c 24 10 48 c7 c6 c0 89 cb 8a ba 53 09 00 00 89 d9 e8
RSP: 0018:ffffc900014df740 EFLAGS: 00010246
RAX: 6c7596ed8d7f5c00 RBX: 00000000ffffffe4 RCX: ffff888024243b80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900014df978 R08: ffffffff8166491c R09: ffffed1017344f24
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801e020001
R13: dffffc0000000000 R14: ffff888078a691b0 R15: ffff888078a69050
FS: 000055555751b300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2eb05242a9 CR3: 0000000022615000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__btrfs_end_transaction+0x296/0x780 fs/btrfs/transaction.c:1007
btrfs_inc_block_group_ro+0x583/0x5f0 fs/btrfs/block-group.c:2610
btrfs_relocate_block_group+0x3ec/0xcb0 fs/btrfs/relocation.c:4012
btrfs_relocate_chunk+0xac/0x270 fs/btrfs/volumes.c:3280
__btrfs_balance+0x185e/0x27c0 fs/btrfs/volumes.c:4010
btrfs_balance+0xd40/0x14a0 fs/btrfs/volumes.c:4400
btrfs_ioctl_balance+0x643/0x7d0 fs/btrfs/ioctl.c:4130
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f5284bceb19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff33dae9a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f5284bceb19
RDX: 0000000020001200 RSI: 00000000c4009420 RDI: 0000000000000004
RBP: 00007f5284b8e3b0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000050e7 R11: 0000000000000246 R12: 00007f5284b8e440
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit a1912f712188291f9d7d434fba155461f1ebef66
git tree: upstream
Author: Josef Bacik <jo...@toxicpanda.com>
Date: Wed Nov 22 17:17:55 2023 +0000

btrfs: remove code for inode_cache and recovery mount options

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a204fbe80000

kernel config: https://syzkaller.appspot.com/x/.config?x=717fa62bb7f0fe9
dashboard link: https://syzkaller.appspot.com/bug?extid=ecef109a157e70c06e25

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1012fabd280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1373c848a80000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection