[v6.1] WARNING in btrfs_create_pending_block_groups

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1321ab403b38 Linux 6.1.45
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12456ef7a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5afeea223ff7d6fa
dashboard link: https://syzkaller.appspot.com/bug?extid=5d608f4f385ba0eb8e16
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13316203a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fd236fa80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df0f614deffc/disk-1321ab40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df0f1be30831/vmlinux-1321ab40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e190f335ac9/bzImage-1321ab40.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2dd6b504def9/mount_0.gz

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

BTRFS warning (device loop0): the 'inode_cache' option is deprecated and has no effect since 5.11
BTRFS info (device loop0): doing ref verification
BTRFS info (device loop0): using free space tree
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: 3507 at fs/btrfs/block-group.c:2455 btrfs_create_pending_block_groups+0x1025/0x12a0 fs/btrfs/block-group.c:2455
Modules linked in:
CPU: 0 PID: 3507 Comm: syz-executor129 Not tainted 6.1.45-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:btrfs_create_pending_block_groups+0x1025/0x12a0 fs/btrfs/block-group.c:2455
Code: ba 9e 09 00 00 44 89 f9 e8 c8 4c d8 06 4c 8b 6c 24 10 e9 5d f5 ff ff e8 d9 64 df fd 48 c7 c7 a0 ae 2f 8b 89 de e8 3b c2 a7 fd <0f> 0b e9 56 ff ff ff e8 bf 64 df fd 48 c7 c7 a0 ae 2f 8b 44 89 e6
RSP: 0018:ffffc900039ef6c0 EFLAGS: 00010246
RAX: a64685b8bfa56700 RBX: 00000000ffffffe4 RCX: ffff888028da0000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900039ef950 R08: ffffffff81525dfe R09: fffff5200073de51
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888018aed058
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff888079618001
FS: 0000555555d5a380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556019cfc860 CR3: 000000001a3fa000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__btrfs_end_transaction+0x2be/0x7b0 fs/btrfs/transaction.c:996
btrfs_inc_block_group_ro+0x644/0x6f0 fs/btrfs/block-group.c:2711
btrfs_relocate_block_group+0x439/0xd70 fs/btrfs/relocation.c:4011
btrfs_relocate_chunk+0x128/0x3b0 fs/btrfs/volumes.c:3296
__btrfs_balance+0x1c16/0x27d0 fs/btrfs/volumes.c:4033
btrfs_balance+0xbd4/0x10c0 fs/btrfs/volumes.c:4409
btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:4488
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
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+0x63/0xcd
RIP: 0033:0x7fd705355979
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff054058a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007fd705355979
RDX: 0000000020001200 RSI: 00000000c4009420 RDI: 0000000000000004
RBP: 00007fd7053cd610 R08: 0000000000000000 R09: 00007fff05405a78
R10: 00000000000050e7 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff05405a68 R14: 0000000000000001 R15: 0000000000000001
</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