On Oct 13, 2024, at 22:27, syzbot 
<[email protected]> wrote:
> 
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    75b607fab38d Merge tag 'sched_ext-for-6.12-rc2-fixes' of g..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10d35780580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=7a3fccdd0bb995
> 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=14560f07980000
> 
> Downloadable assets:
> disk image: 
> https://storage.googleapis.com/syzbot-assets/283eaf72a57c/disk-75b607fa.raw.xz
> vmlinux: 
> https://storage.googleapis.com/syzbot-assets/a721235f5b80/vmlinux-75b607fa.xz
> kernel image: 
> https://storage.googleapis.com/syzbot-assets/f5219ace4d70/bzImage-75b607fa.xz
> mounted in repro: 
> https://storage.googleapis.com/syzbot-assets/c65430058ea3/mount_0.gz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: [email protected]
> 
> 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: 1 UID: 0 PID: 5433 Comm: syz.3.18 Not tainted 
> 6.12.0-rc2-syzkaller-00058-g75b607fab38d #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS 
> Google 09/13/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:26
> __bch2_fsck_err+0x1167/0x15f0 fs/bcachefs/error.c:422
> bch2_read_superblock_clean+0x3b4/0x520 fs/bcachefs/sb-clean.c:152
> bch2_fs_recovery+0x1f4/0x39c0 fs/bcachefs/recovery.c:639
> bch2_fs_start+0x356/0x5b0 fs/bcachefs/super.c:1037
> bch2_fs_get_tree+0xd68/0x1710 fs/bcachefs/fs.c:2080
> vfs_get_tree+0x90/0x2b0 fs/super.c:1800
> do_new_mount+0x2be/0xb40 fs/namespace.c:3507
> do_mount fs/namespace.c:3847 [inline]
> __do_sys_mount fs/namespace.c:4055 [inline]
> __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4032
> 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:0x7fb67417f79a
> 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:00007fb674f20e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
> RAX: ffffffffffffffda RBX: 00007fb674f20ef0 RCX: 00007fb67417f79a
> RDX: 00000000200058c0 RSI: 0000000020000100 RDI: 00007fb674f20eb0
> RBP: 00000000200058c0 R08: 00007fb674f20ef0 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000100
> R13: 00007fb674f20eb0 R14: 0000000000005957 R15: 0000000020000080
> </TASK>
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
> 
> 
> ---
> 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
> 

#syz invalid


Reply via email to