Hello,
syzbot found the following issue on:
HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=116b2bc2c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link:
https://syzkaller.appspot.com/bug?extid=a45b0ad66e4d43324f99
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/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a45b0a...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3666 at fs/btrfs/space-info.h:122 btrfs_space_info_update_bytes_may_use+0x3cd/0x8a0
Modules linked in:
CPU: 1 PID: 3666 Comm: syz-executor.5 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:btrfs_space_info_update_bytes_may_use+0x3cd/0x8a0 fs/btrfs/space-info.h:122
Code: 25 00 00 74 08 4c 89 ff e8 70 64 31 fe 49 8b 1f 48 89 df 48 8b 6c 24 18 48 89 ee e8 ad 01 db fd 48 39 eb 73 14 e8 c3 ff da fd <0f> 0b 45 31 f6 43 80 7c 25 00 00 75 ac eb b2 e8 af ff da fd 43 80
RSP: 0018:ffffc900044af9f8 EFLAGS: 00010293
RAX: ffffffff83af615d RBX: 00000000000df000 RCX: ffff88802613ba80
RDX: 0000000000000000 RSI: 00000000000e0000 RDI: 00000000000df000
RBP: 00000000000e0000 R08: ffffffff83af6153 R09: fffffbfff1ca5dae
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff11004c47e0c R14: fffffffffff20000 R15: ffff88802623f060
FS: 0000555556dc9400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000562dad7c4788 CR3: 00000000315e8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_space_info_free_bytes_may_use fs/btrfs/space-info.h:154 [inline]
block_rsv_release_bytes fs/btrfs/block-rsv.c:151 [inline]
btrfs_block_rsv_release+0x43d/0x520 fs/btrfs/block-rsv.c:295
btrfs_release_global_block_rsv+0x2f/0x250 fs/btrfs/block-rsv.c:463
btrfs_free_block_groups+0xa31/0xe20 fs/btrfs/block-group.c:4052
close_ctree+0x6db/0xc35 fs/btrfs/disk-io.c:4719
generic_shutdown_super+0x130/0x340 fs/super.c:492
kill_anon_super+0x37/0x60 fs/super.c:1099
btrfs_kill_super+0x3d/0x50 fs/btrfs/super.c:2441
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/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:203
__syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
syscall_exit_to_user_mode+0x60/0x2d0 kernel/entry/common.c:296
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb55ac8d567
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:00007ffd3049c0c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fb55ac8d567
RDX: 00007ffd3049c19a RSI: 000000000000000a RDI: 00007ffd3049c190
RBP: 00007ffd3049c190 R08: 00000000ffffffff R09: 00007ffd3049bf60
R10: 0000555556dca8b3 R11: 0000000000000246 R12: 00007fb55ace6b74
R13: 00007ffd3049d250 R14: 0000555556dca810 R15: 00007ffd3049d290
</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.