From: syzbot <syzbot+e3f91c76099a777cbf16@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 BUG in do_bch2_trans_commit_to_journal_replay
Date: Mon, 21 Jul 2025 03:46:35 -0700 [thread overview]
Message-ID: <687e1a8b.a70a0220.693ce.00ec.GAE@google.com> (raw)
In-Reply-To: <687c89c0.a70a0220.693ce.00b1.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: d086c886ceb9 Add linux-next specific files for 20250718
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=126b41bc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc0cd9fdf69889c3
dashboard link: https://syzkaller.appspot.com/bug?extid=e3f91c76099a777cbf16
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12227722580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4435f80a19c4/disk-d086c886.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9a7dc57a5ea3/vmlinux-d086c886.xz
kernel image: https://storage.googleapis.com/syzbot-assets/da9f2dc22ae1/bzImage-d086c886.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f5e4ca95b41f/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e3f91c76099a777cbf16@syzkaller.appspotmail.com
allowing incompatible features above 0.0: (unknown version)
features: lz4,new_siphash,inline_data,new_extent_overwrite,btree_ptr_v2,new_varint,journal_no_flush,alloc_v2,extents_across_btree_nodes
bcachefs (loop0): Using encoding defined by superblock: utf8-12.1.0
bcachefs (loop0): initializing new filesystem
------------[ cut here ]------------
kernel BUG at fs/bcachefs/btree_trans_commit.c:1027!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 11141 Comm: syz.0.833 Not tainted 6.16.0-rc6-next-20250718-syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:do_bch2_trans_commit_to_journal_replay+0x10f3/0x1120 fs/bcachefs/btree_trans_commit.c:1027
Code: 48 c7 c1 79 7b 99 8d 49 89 c0 e8 f8 7a 2b 00 4c 89 ff e8 10 c7 0d 00 48 8b 7c 24 68 e8 d6 1b 00 00 90 0f 0b e8 4e e3 92 fd 90 <0f> 0b e8 46 e3 92 fd eb ad e8 3f e3 92 fd eb a6 e8 38 e3 92 fd 90
RSP: 0018:ffffc9000401edb8 EFLAGS: 00010293
RAX: ffffffff842ccdc2 RBX: 00000000fffff7ab RCX: ffff888030303c00
RDX: 0000000000000000 RSI: 00000000fffff7ab RDI: 0000000000000000
RBP: ffff888076024000 R08: ffff888045c049e3 R09: 1ffff11008b8093c
R10: dffffc0000000000 R11: ffffed1008b8093d R12: ffff888076024028
R13: 0000000000000000 R14: ffff8880760240d2 R15: ffff888030a90080
FS: 00007f01a1c236c0(0000) GS:ffff888125be3000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff07b402150 CR3: 000000006968a000 CR4: 00000000003526f0
Call Trace:
<TASK>
__bch2_trans_commit+0x1b13/0x8a70 fs/bcachefs/btree_trans_commit.c:1060
bch2_trans_commit fs/bcachefs/btree_update.h:270 [inline]
bch2_dev_usage_init+0x22c/0x3f0 fs/bcachefs/disk_accounting.c:934
bch2_fs_initialize+0x4b5/0xe60 fs/bcachefs/recovery.c:1179
bch2_fs_start+0xa00/0xcc0 fs/bcachefs/super.c:1217
bch2_fs_get_tree+0xb39/0x1540 fs/bcachefs/fs.c:2456
vfs_get_tree+0x92/0x2b0 fs/super.c:1815
do_new_mount+0x2a2/0x9e0 fs/namespace.c:3805
do_mount fs/namespace.c:4133 [inline]
__do_sys_mount fs/namespace.c:4344 [inline]
__se_sys_mount+0x317/0x410 fs/namespace.c:4321
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f01a0d9014a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f01a1c22e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f01a1c22ef0 RCX: 00007f01a0d9014a
RDX: 0000200000000140 RSI: 0000200000000100 RDI: 00007f01a1c22eb0
RBP: 0000200000000140 R08: 00007f01a1c22ef0 R09: 0000000002800000
R10: 0000000002800000 R11: 0000000000000246 R12: 0000200000000100
R13: 00007f01a1c22eb0 R14: 0000000000005a7a R15: 0000200000000340
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_bch2_trans_commit_to_journal_replay+0x10f3/0x1120 fs/bcachefs/btree_trans_commit.c:1027
Code: 48 c7 c1 79 7b 99 8d 49 89 c0 e8 f8 7a 2b 00 4c 89 ff e8 10 c7 0d 00 48 8b 7c 24 68 e8 d6 1b 00 00 90 0f 0b e8 4e e3 92 fd 90 <0f> 0b e8 46 e3 92 fd eb ad e8 3f e3 92 fd eb a6 e8 38 e3 92 fd 90
RSP: 0018:ffffc9000401edb8 EFLAGS: 00010293
RAX: ffffffff842ccdc2 RBX: 00000000fffff7ab RCX: ffff888030303c00
RDX: 0000000000000000 RSI: 00000000fffff7ab RDI: 0000000000000000
RBP: ffff888076024000 R08: ffff888045c049e3 R09: 1ffff11008b8093c
R10: dffffc0000000000 R11: ffffed1008b8093d R12: ffff888076024028
R13: 0000000000000000 R14: ffff8880760240d2 R15: ffff888030a90080
FS: 00007f01a1c236c0(0000) GS:ffff888125be3000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0f4c3e5000 CR3: 000000006968a000 CR4: 00000000003526f0
---
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:[~2025-07-21 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 6:16 [syzbot] [bcachefs?] kernel BUG in do_bch2_trans_commit_to_journal_replay syzbot
2025-07-21 10:46 ` syzbot [this message]
2025-07-22 16:20 ` Kent Overstreet
2025-07-22 18:44 ` syzbot
2025-07-23 1:12 ` Kent Overstreet
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=687e1a8b.a70a0220.693ce.00ec.GAE@google.com \
--to=syzbot+e3f91c76099a777cbf16@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 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.