From: syzbot <syzbot+803e4cb8245b52928347@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in btrfs_create_qgroup
Date: Thu, 11 Dec 2025 16:46:03 -0800 [thread overview]
Message-ID: <693b65cb.a70a0220.33cd7b.003e.GAE@google.com> (raw)
In-Reply-To: <20251212003024.3563901-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in btrfs_space_info_update_bytes_may_use
BTRFS info (device loop0 state EA): last unmount of filesystem 395ef67a-297e-477c-816d-cd80a5b93e5d
------------[ cut here ]------------
WARNING: fs/btrfs/space-info.h:257 at btrfs_space_info_update_bytes_may_use+0x318/0x600 fs/btrfs/space-info.h:257, CPU#0: syz-executor/5765
Modules linked in:
CPU: 0 UID: 0 PID: 5765 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:btrfs_space_info_update_bytes_may_use+0x318/0x600 fs/btrfs/space-info.h:257
Code: 00 00 74 08 4c 89 ff e8 06 ae 32 fe 4d 8b 27 4c 89 e7 48 8b 6c 24 18 48 89 ee e8 d3 d3 ca fd 49 39 ec 73 1c e8 69 d1 ca fd 90 <0f> 0b 90 31 db 43 80 7c 35 00 00 0f 85 48 ff ff ff e9 4b ff ff ff
RSP: 0018:ffffc9000268f9d0 EFLAGS: 00010293
RAX: ffffffff83f6eee7 RBX: ffffffffffea1000 RCX: ffff888000c18000
RDX: 0000000000000000 RSI: 000000000015f000 RDI: 000000000015e000
RBP: 000000000015f000 R08: ffffffff8fa21877 R09: 1ffffffff1f4430e
R10: dffffc0000000000 R11: fffffbfff1f4430f R12: 000000000015e000
R13: 1ffff110022dc410 R14: dffffc0000000000 R15: ffff8880116e2080
FS: 0000555564980500(0000) GS:ffff88808d22f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055556499b5c8 CR3: 0000000023114000 CR4: 0000000000352ef0
Call Trace:
<TASK>
btrfs_space_info_free_bytes_may_use fs/btrfs/space-info.h:294 [inline]
block_rsv_release_bytes fs/btrfs/block-rsv.c:153 [inline]
btrfs_block_rsv_release+0x462/0x570 fs/btrfs/block-rsv.c:290
btrfs_release_global_block_rsv+0x33/0x270 fs/btrfs/block-rsv.c:455
btrfs_free_block_groups+0xcbf/0xfd0 fs/btrfs/block-group.c:4579
close_ctree+0x7bc/0x1380 fs/btrfs/disk-io.c:4410
generic_shutdown_super+0x135/0x2c0 fs/super.c:643
kill_anon_super+0x3b/0x70 fs/super.c:1289
btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2129
deactivate_locked_super+0xbc/0x130 fs/super.c:474
cleanup_mnt+0x425/0x4c0 fs/namespace.c:1318
task_work_run+0x1d4/0x260 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:44 [inline]
exit_to_user_mode_loop+0xff/0x4f0 kernel/entry/common.c:75
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]
do_syscall_64+0x2e3/0xf80 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1756990af7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 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 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc9d03bb88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f1756a13d7d RCX: 00007f1756990af7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc9d03bc40
RBP: 00007ffc9d03bc40 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc9d03ccd0
R13: 00007f1756a13d7d R14: 00000000000277e0 R15: 00007ffc9d03cd10
</TASK>
Tested on:
commit: d358e525 Merge tag 'for-6.19/dm-changes' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13299592580000
kernel config: https://syzkaller.appspot.com/x/.config?x=de48dccdf203ea90
dashboard link: https://syzkaller.appspot.com/bug?extid=803e4cb8245b52928347
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=10e4561a580000
next parent reply other threads:[~2025-12-12 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251212003024.3563901-1-kartikey406@gmail.com>
2025-12-12 0:46 ` syzbot [this message]
2025-12-11 22:50 [syzbot] [btrfs?] kernel BUG in btrfs_create_qgroup syzbot
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=693b65cb.a70a0220.33cd7b.003e.GAE@google.com \
--to=syzbot+803e4cb8245b52928347@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.