Hello, syzbot found the following issue on: HEAD commit: 6a71d2909427 Merge branch 'for-next/core' into for-kernelci 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=125b5ae7180000 kernel config: https://syzkaller.appspot.com/x/.config?x=fca646cf17cc616b dashboard link: https://syzkaller.appspot.com/bug?extid=85d8bf8b2759214b194b 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=13d1eb73180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171c9a80980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c77d21fa1405/disk-6a71d290.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/429fcd369816/vmlinux-6a71d290.xz kernel image: https://storage.googleapis.com/syzbot-assets/d3d8a4b85112/Image-6a71d290.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/19eeb68a57c8/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+85d8bf8b2759214b194b@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 9973 at fs/ext4/ext4_jbd2.c:73 __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105 Modules linked in: CPU: 0 PID: 9973 Comm: syz-executor391 Not tainted 6.9.0-rc4-syzkaller-g6a71d2909427 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 pstate: 80401005 (Nzcv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--) pc : __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105 lr : ext4_journal_check_start fs/ext4/ext4_jbd2.c:73 [inline] lr : __ext4_journal_start_sb+0x440/0x92c fs/ext4/ext4_jbd2.c:105 sp : ffff80009c0474b0 x29: ffff80009c0474c0 x28: 1fffe00018de8cc7 x27: dfff800000000000 x26: 0000000070818001 x25: ffff0000c6f46638 x24: ffff0000c6f46000 x23: 0000000000000001 x22: 0000000000000000 x21: 0000000000000000 x20: ffffffffffffffe2 x19: ffff0000d9ac6280 x18: 1fffe000367b9596 x17: ffff80008ee7d000 x16: ffff800080332544 x15: 0000000000000001 x14: 1fffe0001b750b2b x13: 0000000000000000 x12: 0000000000000000 x11: ffff60001b750b2c x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000dbfe8000 x7 : ffff800080c13aac x6 : 0000000000000008 x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000000 Call trace: __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105 ext4_sample_last_mounted fs/ext4/file.c:837 [inline] ext4_file_open+0x3c8/0x590 fs/ext4/file.c:866 do_dentry_open+0x778/0x12b4 fs/open.c:955 vfs_open+0x7c/0x90 fs/open.c:1089 do_open fs/namei.c:3642 [inline] path_openat+0x1f6c/0x2830 fs/namei.c:3799 do_filp_open+0x1bc/0x3cc fs/namei.c:3826 do_sys_openat2+0x124/0x1b8 fs/open.c:1406 do_sys_open fs/open.c:1421 [inline] __do_sys_openat fs/open.c:1437 [inline] __se_sys_openat fs/open.c:1432 [inline] __arm64_sys_openat+0x1f0/0x240 fs/open.c:1432 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 irq event stamp: 186 hardirqs last enabled at (185): [<ffff800080c164c4>] seqcount_lockdep_reader_access+0x80/0x100 include/linux/seqlock.h:74 hardirqs last disabled at (186): [<ffff80008ae6da08>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470 softirqs last enabled at (8): [<ffff800080031848>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32 softirqs last disabled at (6): [<ffff800080031814>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19 ---[ 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 syzkaller@xxxxxxxxxxxxxxxx. 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
