Hello, syzbot found the following issue on:
HEAD commit: 526116b79e8c KVM: arm64: Shave a few bytes from the EL2 id.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=17e78c30580000 kernel config: https://syzkaller.appspot.com/x/.config?x=e39b0b4b1ace5bc0 dashboard link: https://syzkaller.appspot.com/bug?extid=859300e61790263514a3 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164488a7980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17052a5f980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/2f7b2b08fdad/disk-526116b7.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/b69595b63015/vmlinux-526116b7.xz kernel image: https://storage.googleapis.com/syzbot-assets/39fd415ada60/Image-526116b7.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/bc1232192aa1/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] bcachefs (loop0): bch2_write_super(): fatal error loop0: Superblock write was silently dropped! (seq 0 expected 53) bcachefs (loop0): fatal error - emergency read only ------------[ cut here ]------------ kernel BUG at fs/bcachefs/journal.h:375! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 UID: 0 PID: 11 Comm: kworker/u8:0 Not tainted 6.12.0-rc4-syzkaller-g526116b79e8c #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btree_update btree_interior_update_work pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : bch2_journal_res_get+0x6fc/0x710 fs/bcachefs/journal.h:375 lr : bch2_journal_res_get+0x6fc/0x710 fs/bcachefs/journal.h:375 sp : ffff8000978b7560 x29: ffff8000978b7650 x28: 000000000000000e x27: ffff0000e0aca500 x26: 1fffe0001b9a901a x25: dfff800000000000 x24: 1ffff00012f16ebc x23: 0000000000000044 x22: ffff8000978b75e0 x21: ffff0000e0aca500 x20: 0000000000000004 x19: ffff0000dcd480d0 x18: ffff8000978b6740 x17: 0000000000000000 x16: ffff80008b3d3d08 x15: ffff700012f16e9c x14: 1ffff00012f16e9c x13: 0000000000000004 x12: ffffffffffffffff x11: ffff700012f16e9c x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000c19dbc80 x7 : 0000000000000000 x6 : 0000000000000105 x5 : ffff8000978b7308 x4 : 0000000000000000 x3 : 000000000000000e x2 : 0000000000000044 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: bch2_journal_res_get+0x6fc/0x710 fs/bcachefs/journal.h:375 (P) bch2_journal_res_get+0x6fc/0x710 fs/bcachefs/journal.h:375 (L) bch2_trans_journal_res_get fs/bcachefs/btree_trans_commit.c:350 [inline] bch2_trans_commit_write_locked fs/bcachefs/btree_trans_commit.c:668 [inline] do_bch2_trans_commit fs/bcachefs/btree_trans_commit.c:900 [inline] __bch2_trans_commit+0x2a00/0x6604 fs/bcachefs/btree_trans_commit.c:1121 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+0xd40/0x1e00 fs/bcachefs/btree_update_interior.c:866 process_one_work+0x7bc/0x1600 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x97c/0xeec kernel/workqueue.c:3391 kthread+0x288/0x310 kernel/kthread.c:389 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862 Code: 955b1ed6 97749ac7 d4210000 97749ac5 (d4210000) ---[ end trace 0000000000000000 ]--- --- 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
