[syzbot] [btrfs?] WARNING in btrfs_put_block_group

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8e41e0a57566 Revert "ACPICA: Events: Support fixed PCIe wa..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11a7e1bfc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4afb87f3ec27b7fd
dashboard link: https://syzkaller.appspot.com/bug?extid=e38c6fff39c0d7d6f121
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/69cc9a5732ed/disk-8e41e0a5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f32a5c8e9e68/vmlinux-8e41e0a5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b56460ca80d/bzImage-8e41e0a5.xz

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

BTRFS info (device loop5): at unmount dio bytes count 8192
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5108 at fs/btrfs/block-group.c:152 btrfs_put_block_group+0x257/0x2b0
Modules linked in:
CPU: 0 PID: 5108 Comm: syz-executor.5 Not tainted 6.3.0-rc7-syzkaller-00181-g8e41e0a57566 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:btrfs_put_block_group+0x257/0x2b0 fs/btrfs/block-group.c:152
Code: fe e8 fd 28 e2 fd 0f 0b e9 4a fe ff ff e8 f1 28 e2 fd 48 89 df be 03 00 00 00 5b 41 5e 41 5f 5d e9 fe eb 87 00 e8 d9 28 e2 fd <0f> 0b e9 1c ff ff ff e8 cd 28 e2 fd 0f 0b 4c 89 f0 48 c1 e8 03 42
RSP: 0018:ffffc90003f9fa90 EFLAGS: 00010293
RAX: ffffffff83a850b7 RBX: 0000000000002000 RCX: ffff888020419d40
RDX: 0000000000000000 RSI: 0000000000002000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83a84fcc R09: ffffed100ea7db41
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88802f07c318
R13: dffffc0000000000 R14: ffff88802f07c000 R15: dffffc0000000000
FS: 0000555555b01400(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffa6ebc8300 CR3: 000000002d689000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_free_block_groups+0x9b0/0xe80 fs/btrfs/block-group.c:4272
close_ctree+0x742/0xd30 fs/btrfs/disk-io.c:4649
generic_shutdown_super+0x134/0x340 fs/super.c:500
kill_anon_super+0x3b/0x60 fs/super.c:1107
btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2133
deactivate_locked_super+0xa4/0x110 fs/super.c:331
cleanup_mnt+0x426/0x4c0 fs/namespace.c:1177
task_work_run+0x24a/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x64/0x280 kernel/entry/common.c:297
do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f03aec8d5d7
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 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:00007ffeb62f6788 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f03aec8d5d7
RDX: 00007ffeb62f685b RSI: 000000000000000a RDI: 00007ffeb62f6850
RBP: 00007ffeb62f6850 R08: 00000000ffffffff R09: 00007ffeb62f6620
R10: 0000555555b028b3 R11: 0000000000000246 R12: 00007f03aece6cdc
R13: 00007ffeb62f7910 R14: 0000555555b02810 R15: 00007ffeb62f7950
</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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: be3ca57cfb77 Merge tag 'media/v6.7-1' of git://git.kernel...
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11163cdf680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ffa1cec3b40f3ce
dashboard link: https://syzkaller.appspot.com/bug?extid=e38c6fff39c0d7d6f121
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f3c760e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1110877f680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9e42e209afb1/disk-be3ca57c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/faad7e361a8e/vmlinux-be3ca57c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/56d812634b0d/bzImage-be3ca57c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2e2950f94580/mount_0.gz

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

BTRFS info (device loop2): at unmount dio bytes count 45056
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5067 at fs/btrfs/block-group.c:159 btrfs_put_block_group fs/btrfs/block-group.c:159 [inline]
WARNING: CPU: 0 PID: 5067 at fs/btrfs/block-group.c:159 btrfs_put_block_group+0x2c9/0x330 fs/btrfs/block-group.c:146
Modules linked in:
CPU: 0 PID: 5067 Comm: syz-executor383 Not tainted 6.6.0-syzkaller-15029-gbe3ca57cfb77 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:btrfs_put_block_group fs/btrfs/block-group.c:159 [inline]
RIP: 0010:btrfs_put_block_group+0x2c9/0x330 fs/btrfs/block-group.c:146
Code: 48 8d b8 e0 15 00 00 e8 f5 70 01 00 e9 b8 fe ff ff e8 db ca 43 fe e9 1f fe ff ff e8 d1 ca 43 fe e9 d7 fd ff ff e8 07 da ec fd <0f> 0b e9 61 fe ff ff e8 bb ca 43 fe e9 b5 fe ff ff e8 b1 ca 43 fe
RSP: 0018:ffffc90003a1fb48 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888026356000 RCX: ffffffff839bc0d8
RDX: ffff888061868000 RSI: ffffffff839bc279 RDI: 0000000000000007
RBP: 000000000000b000 R08: 0000000000000007 R09: 0000000000000000
R10: 000000000000b000 R11: 1ffff11004f89c32 R12: ffff888060c28000
R13: 0000000000000001 R14: ffff888026356160 R15: ffff888026356000
FS: 0000555556d0c380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f7172fd2100 CR3: 000000007ef04000 CR4: 0000000000350ef0
Call Trace:
<TASK>
btrfs_free_block_groups+0x9f5/0x13d0 fs/btrfs/block-group.c:4360
close_ctree+0x8c4/0xdd0 fs/btrfs/disk-io.c:4389
generic_shutdown_super+0x161/0x3c0 fs/super.c:696
kill_anon_super+0x3a/0x60 fs/super.c:1295
btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2097
deactivate_locked_super+0xbc/0x1a0 fs/super.c:484
deactivate_super+0xde/0x100 fs/super.c:517
cleanup_mnt+0x222/0x450 fs/namespace.c:1256
task_work_run+0x14d/0x240 kernel/task_work.c:180
ptrace_notify+0x10c/0x130 kernel/signal.c:2399
ptrace_report_syscall include/linux/ptrace.h:411 [inline]
ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
syscall_exit_work kernel/entry/common.c:251 [inline]
syscall_exit_to_user_mode_prepare+0x120/0x220 kernel/entry/common.c:278
__syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
syscall_exit_to_user_mode+0xd/0x60 kernel/entry/common.c:296
do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:88
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f7172f56677
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe85c2eed8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000020373 RCX: 00007f7172f56677
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffe85c2ef90
RBP: 00007ffe85c2ef90 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffe85c30000
R13: 0000555556d0d6c0 R14: 431bde82d7b634db R15: 00007ffe85c30020
</TASK>


---
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.