Hello, syzbot found the following issue on: HEAD commit: 707081b61156 Merge branch 'for-next/core', remote-tracking.. 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=106d6d15180000 kernel config: https://syzkaller.appspot.com/x/.config?x=caeac3f3565b057a dashboard link: https://syzkaller.appspot.com/bug?extid=fe18c63ce101f2b358bb 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=156040bd180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149d2ead180000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6cad68bf7532/disk-707081b6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1a27e5400778/vmlinux-707081b6.xz kernel image: https://storage.googleapis.com/syzbot-assets/67dfc53755d0/Image-707081b6.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/e198b7a8a7f2/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+fe18c63ce101f2b358bb@xxxxxxxxxxxxxxxxxxxxxxxxx loop0: detected capacity change from 0 to 4096 ntfs: volume version 3.1. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 6164 at fs/exec.c:940 do_open_execat+0x2bc/0x3bc Modules linked in: CPU: 0 PID: 6164 Comm: syz-executor379 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : do_open_execat+0x2bc/0x3bc lr : do_open_execat+0x2b8/0x3bc fs/exec.c:939 sp : ffff8000977a7b60 x29: ffff8000977a7bd0 x28: 0000000000000000 x27: ffff0000d609da2c x26: 00000000ffffff9c x25: dfff800000000000 x24: ffff700012ef4f6c x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000 x20: fffffffffffffff3 x19: ffff0000d5ba0000 x18: ffff8000977a7100 x17: 000000000000c791 x16: ffff80008aca6dc0 x15: 0000000000000002 x14: 1ffff00012ef4f34 x13: 0000000000000000 x12: 0000000000000000 x11: ffff700012ef4f36 x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000d609da00 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000008000 Call trace: do_open_execat+0x2bc/0x3bc alloc_bprm+0x44/0x934 fs/exec.c:1541 do_execveat_common+0x158/0x814 fs/exec.c:1935 do_execveat fs/exec.c:2069 [inline] __do_sys_execveat fs/exec.c:2143 [inline] __se_sys_execveat fs/exec.c:2137 [inline] __arm64_sys_execveat+0xd0/0xec fs/exec.c:2137 __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: 24796 hardirqs last enabled at (24795): [<ffff80008ae5ce28>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline] hardirqs last enabled at (24795): [<ffff80008ae5ce28>] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:194 hardirqs last disabled at (24796): [<ffff80008ad66988>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470 softirqs last enabled at (24766): [<ffff80008002189c>] softirq_handle_end kernel/softirq.c:399 [inline] softirqs last enabled at (24766): [<ffff80008002189c>] __do_softirq+0xac8/0xce4 kernel/softirq.c:582 softirqs last disabled at (24737): [<ffff80008002ab48>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:81 ---[ 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
