From: syzbot <syzbot+e6ea15c610261d2106ba@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel panic: bcachefs (loop3): panic after error
Date: Thu, 19 Dec 2024 15:38:34 -0800 [thread overview]
Message-ID: <6764ae7a.050a0220.36de9c.0001.GAE@google.com> (raw)
In-Reply-To: <670bd8cc.050a0220.4cbc0.0031.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 8503810115fb Add linux-next specific files for 20241219
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12200fe8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=26a4b4cc7f877b28
dashboard link: https://syzkaller.appspot.com/bug?extid=e6ea15c610261d2106ba
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=116462df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17aaf730580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8e84022cbe98/disk-85038101.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/112a23063d67/vmlinux-85038101.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3778558f0562/bzImage-85038101.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ca00766e5d34/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e6ea15c610261d2106ba@syzkaller.appspotmail.com
bcachefs (loop3): starting version 1.7: mi_btree_bitmap opts=errors=panic,metadata_checksum=crc64,data_checksum=none,compression=lz4,background_compression=gzip,no_splitbrain_check,nocow
superblock marked clean but clean section not present, shutting down
Kernel panic - not syncing: bcachefs (loop3): panic after error
CPU: 0 UID: 0 PID: 5901 Comm: syz-executor172 Not tainted 6.13.0-rc3-next-20241219-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
panic+0x349/0x880 kernel/panic.c:354
bch2_inconsistent_error+0x146/0x150 fs/bcachefs/error.c:28
__bch2_fsck_err+0x10de/0x1420 fs/bcachefs/error.c:438
bch2_read_superblock_clean+0x166/0x260 fs/bcachefs/sb-clean.c:156
bch2_fs_recovery+0x1e6/0x3de0 fs/bcachefs/recovery.c:707
bch2_fs_start+0x37c/0x610 fs/bcachefs/super.c:1032
bch2_fs_get_tree+0xd8d/0x1740 fs/bcachefs/fs.c:2200
vfs_get_tree+0x90/0x2b0 fs/super.c:1814
do_new_mount+0x2be/0xb40 fs/namespace.c:3556
do_mount fs/namespace.c:3896 [inline]
__do_sys_mount fs/namespace.c:4107 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4084
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb599d79a6a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe81ab3658 EFLAGS: 00000282 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb599d79a6a
RDX: 00000000200058c0 RSI: 0000000020000100 RDI: 00007ffe81ab36b0
RBP: 0000000000000004 R08: 00007ffe81ab36f0 R09: 0000000000005951
R10: 0000000000000000 R11: 0000000000000282 R12: 00007ffe81ab36f0
R13: 0000000001000000 R14: 0000000000000003 R15: 0000000000000000
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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.
next prev parent reply other threads:[~2024-12-19 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 14:27 [syzbot] [bcachefs?] kernel panic: bcachefs (loop3): panic after error syzbot
2024-10-13 17:41 ` Kent Overstreet
2024-12-19 23:38 ` syzbot [this message]
2025-08-08 5:48 ` Alan Huang
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=6764ae7a.050a0220.36de9c.0001.GAE@google.com \
--to=syzbot+e6ea15c610261d2106ba@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox