Hello, syzbot found the following issue on: HEAD commit: c2ee9f594da8 KVM: selftests: Fix build on on non-x86 archi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11dc50a7980000 kernel config: https://syzkaller.appspot.com/x/.config?x=f68c7e50d4601b1 dashboard link: https://syzkaller.appspot.com/bug?extid=aa5a1e52e2ac09339fca compiler: arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c78a5f980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a95430580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/8ead8862021c/non_bootable_disk-c2ee9f59.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/bcc7a230eb09/vmlinux-c2ee9f59.xz kernel image: https://storage.googleapis.com/syzbot-assets/96b5df297c4b/zImage-c2ee9f59.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+aa5a1e52e2ac09339fca@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 3115 at mm/highmem.c:622 kunmap_local_indexed+0x20c/0x224 mm/highmem.c:622 Modules linked in: Kernel panic - not syncing: kernel: panic_on_warn set ... CPU: 1 UID: 0 PID: 3115 Comm: syz-executor704 Not tainted 6.12.0-rc4-syzkaller #0 Hardware name: ARM-Versatile Express Call trace: [<81999930>] (dump_backtrace) from [<81999a2c>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:257) r7:00000000 r6:82622f44 r5:00000000 r4:8203d814 [<81999a14>] (show_stack) from [<819b7ec8>] (__dump_stack lib/dump_stack.c:94 [inline]) [<81999a14>] (show_stack) from [<819b7ec8>] (dump_stack_lvl+0x54/0x7c lib/dump_stack.c:120) [<819b7e74>] (dump_stack_lvl) from [<819b7f08>] (dump_stack+0x18/0x1c lib/dump_stack.c:129) r5:00000000 r4:82870d18 [<819b7ef0>] (dump_stack) from [<8199a558>] (panic+0x120/0x374 kernel/panic.c:354) [<8199a438>] (panic) from [<802420e0>] (check_panic_on_warn kernel/panic.c:243 [inline]) [<8199a438>] (panic) from [<802420e0>] (get_taint+0x0/0x1c kernel/panic.c:238) r3:8260c5c4 r2:00000001 r1:82025be8 r0:8202d650 r7:8048c78c [<8024206c>] (check_panic_on_warn) from [<80242244>] (__warn+0x80/0x188 kernel/panic.c:748) [<802421c4>] (__warn) from [<802424c4>] (warn_slowpath_fmt+0x178/0x1f4 kernel/panic.c:775) r8:00000009 r7:82055258 r6:ec13dd24 r5:841fec00 r4:00000000 [<80242350>] (warn_slowpath_fmt) from [<8048c78c>] (kunmap_local_indexed+0x20c/0x224 mm/highmem.c:622) r10:ffedc0a8 r9:83eb9800 r8:20508000 r7:fffffffe r6:00000003 r5:841fec00 r4:ffedc000 [<8048c580>] (kunmap_local_indexed) from [<80505bb8>] (__kunmap_local include/linux/highmem-internal.h:94 [inline]) [<8048c580>] (kunmap_local_indexed) from [<80505bb8>] (move_pages_pte mm/userfaultfd.c:1329 [inline]) [<8048c580>] (kunmap_local_indexed) from [<80505bb8>] (move_pages+0x7e8/0x149c mm/userfaultfd.c:1730) r7:fffffffe r6:00000000 r5:845ab810 r4:ffeda840 [<805053d0>] (move_pages) from [<80581e18>] (userfaultfd_move fs/userfaultfd.c:1871 [inline]) [<805053d0>] (move_pages) from [<80581e18>] (userfaultfd_ioctl+0x114c/0x2080 fs/userfaultfd.c:1994) r10:83eb9800 r9:ec13de98 r8:00000001 r7:20c16000 r6:00000000 r5:20000080 r4:837d6000 [<80580ccc>] (userfaultfd_ioctl) from [<8052f7d0>] (vfs_ioctl fs/ioctl.c:51 [inline]) [<80580ccc>] (userfaultfd_ioctl) from [<8052f7d0>] (__do_sys_ioctl fs/ioctl.c:907 [inline]) [<80580ccc>] (userfaultfd_ioctl) from [<8052f7d0>] (sys_ioctl+0x134/0xda8 fs/ioctl.c:893) r10:841fec00 r9:843e0840 r8:00000003 r7:20000080 r6:843e0840 r5:00000000 r4:c028aa05 [<8052f69c>] (sys_ioctl) from [<80200060>] (ret_fast_syscall+0x0/0x1c arch/arm/mm/proc-v7.S:67) Exception stack(0xec13dfa8 to 0xec13dff0) dfa0: ffffffff 00000000 00000003 c028aa05 20000080 0000011a dfc0: ffffffff 00000000 0008e058 00000036 7ef11e0c 00000000 00000001 00000000 dfe0: 7ef11c70 7ef11c60 0001072c 0002e8a0 r10:00000036 r9:841fec00 r8:8020029c r7:00000036 r6:0008e058 r5:00000000 r4:ffffffff 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 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
