Hello, syzbot found the following issue on:
HEAD commit: 715ca9dd687f Merge tag 'io_uring-6.12-20241019' of git://g.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=113e6430580000 kernel config: https://syzkaller.appspot.com/x/.config?x=78db40d8379956d9 dashboard link: https://syzkaller.appspot.com/bug?extid=f074d2e31d8d35a6a38c 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=110560a7980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bdc25f980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/bf3787869b5a/disk-715ca9dd.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/b938d885bc17/vmlinux-715ca9dd.xz kernel image: https://storage.googleapis.com/syzbot-assets/9c039de0dde2/bzImage-715ca9dd.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/b049575f12e2/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] bcachefs (loop1): fatal error - emergency read only ------------[ cut here ]------------ kernel BUG at fs/bcachefs/journal.h:375! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 UID: 0 PID: 11 Comm: kworker/u8:0 Not tainted 6.12.0-rc3-syzkaller-00420-g715ca9dd687f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btree_update btree_interior_update_work RIP: 0010:bch2_journal_res_get fs/bcachefs/journal.h:375 [inline] RIP: 0010:bch2_trans_journal_res_get fs/bcachefs/btree_trans_commit.c:350 [inline] RIP: 0010:bch2_trans_commit_write_locked fs/bcachefs/btree_trans_commit.c:668 [inline] RIP: 0010:do_bch2_trans_commit fs/bcachefs/btree_trans_commit.c:900 [inline] RIP: 0010:__bch2_trans_commit+0x9232/0x93c0 fs/bcachefs/btree_trans_commit.c:1121 Code: fd 90 0f 0b e8 3f bb 78 fd 90 0f 0b e8 37 bb 78 fd 90 0f 0b e8 2f bb 78 fd 90 0f 0b e8 27 bb 78 fd 90 0f 0b e8 1f bb 78 fd 90 <0f> 0b e8 17 bb 78 fd 90 0f 0b e8 0f bb 78 fd 90 0f 0b e8 07 bb 78 RSP: 0018:ffffc900001076c0 EFLAGS: 00010293 RAX: ffffffff841c2c91 RBX: 0000000000000000 RCX: ffff88801cebbc00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90000107890 R08: ffffffff841bcfc8 R09: 1ffff1100cd494a8 R10: dffffc0000000000 R11: ffffed100cd494a9 R12: ffff888066a00000 R13: ffff888066a4a500 R14: 0000000000000044 R15: ffff88803060c0d0 FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff942fe8000 CR3: 000000007bcb8000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> bch2_trans_commit fs/bcachefs/btree_update.h:184 [inline] btree_update_nodes_written fs/bcachefs/btree_update_interior.c:728 [inline] btree_interior_update_work+0x1492/0x2b10 fs/bcachefs/btree_update_interior.c:866 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:bch2_journal_res_get fs/bcachefs/journal.h:375 [inline] RIP: 0010:bch2_trans_journal_res_get fs/bcachefs/btree_trans_commit.c:350 [inline] RIP: 0010:bch2_trans_commit_write_locked fs/bcachefs/btree_trans_commit.c:668 [inline] RIP: 0010:do_bch2_trans_commit fs/bcachefs/btree_trans_commit.c:900 [inline] RIP: 0010:__bch2_trans_commit+0x9232/0x93c0 fs/bcachefs/btree_trans_commit.c:1121 Code: fd 90 0f 0b e8 3f bb 78 fd 90 0f 0b e8 37 bb 78 fd 90 0f 0b e8 2f bb 78 fd 90 0f 0b e8 27 bb 78 fd 90 0f 0b e8 1f bb 78 fd 90 <0f> 0b e8 17 bb 78 fd 90 0f 0b e8 0f bb 78 fd 90 0f 0b e8 07 bb 78 RSP: 0018:ffffc900001076c0 EFLAGS: 00010293 RAX: ffffffff841c2c91 RBX: 0000000000000000 RCX: ffff88801cebbc00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90000107890 R08: ffffffff841bcfc8 R09: 1ffff1100cd494a8 R10: dffffc0000000000 R11: ffffed100cd494a9 R12: ffff888066a00000 R13: ffff888066a4a500 R14: 0000000000000044 R15: ffff88803060c0d0 FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff942fff000 CR3: 000000002ce04000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- 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 [email protected]. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title 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. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
