Hello, syzbot found the following issue on: HEAD commit: 7c626ce4bae1 Linux 6.11-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1494eced980000 kernel config: https://syzkaller.appspot.com/x/.config?x=aeb08bd34fa0ed18 dashboard link: https://syzkaller.appspot.com/bug?extid=c61d6962d0b7e698439e compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-7c626ce4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c9ff45c7e113/vmlinux-7c626ce4.xz kernel image: https://storage.googleapis.com/syzbot-assets/f51045fd7afd/bzImage-7c626ce4.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+c61d6962d0b7e698439e@xxxxxxxxxxxxxxxxxxxxxxxxx kmalloc-96 2344KB 2376KB kmem_cache_node 225KB 228KB kmem_cache 203KB 203KB Out of memory and no killable processes... Kernel panic - not syncing: System is deadlocked on memory CPU: 1 UID: 0 PID: 2 Comm: kthreadd Not tainted 6.11.0-rc3-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x3d/0x1f0 lib/dump_stack.c:119 panic+0x6f5/0x7a0 kernel/panic.c:348 out_of_memory+0x15de/0x16b0 mm/oom_kill.c:1170 __alloc_pages_may_oom mm/page_alloc.c:3614 [inline] __alloc_pages_slowpath mm/page_alloc.c:4376 [inline] __alloc_pages_noprof+0x1d89/0x2460 mm/page_alloc.c:4713 alloc_pages_mpol_noprof+0x275/0x610 mm/mempolicy.c:2263 get_free_pages_noprof+0xc/0x40 mm/page_alloc.c:4747 kasan_populate_vmalloc_pte+0x2d/0x160 mm/kasan/shadow.c:304 apply_to_pte_range mm/memory.c:2797 [inline] apply_to_pmd_range mm/memory.c:2841 [inline] apply_to_pud_range mm/memory.c:2877 [inline] apply_to_p4d_range mm/memory.c:2913 [inline] __apply_to_page_range+0x795/0xdd0 mm/memory.c:2947 alloc_vmap_area+0x93e/0x2a70 mm/vmalloc.c:2035 __get_vm_area_node+0x17e/0x2d0 mm/vmalloc.c:3119 __vmalloc_node_range_noprof+0x276/0x1520 mm/vmalloc.c:3801 alloc_thread_stack_node kernel/fork.c:313 [inline] dup_task_struct kernel/fork.c:1113 [inline] copy_process+0x29f5/0x6f50 kernel/fork.c:2204 kernel_clone+0xfd/0x980 kernel/fork.c:2781 kernel_thread+0xc0/0x100 kernel/fork.c:2843 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x4ef/0x7d0 kernel/kthread.c:765 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </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 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 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
