[syzbot] [mm?] kernel panic: System is deadlocked on memory (2)

[syzbot] [mm?] kernel panic: System is deadlocked on memory (2)

[syzbot]

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@syzkaller.appspotmail.com

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@googlegroups.com.

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

Re: [syzbot] [mm?] kernel panic: System is deadlocked on memory (2)

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    848acc8ffe1b Merge tag 'fsverity-for-linus' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1559b649580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=c61d6962d0b7e698439e
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1531be32580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15938bb9580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-848acc8f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6fb497cc0c8d/vmlinux-848acc8f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/663ccee34982/bzImage-848acc8f.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c61d6962d0b7e698439e@syzkaller.appspotmail.com

kmalloc-96              1483KB       1500KB
kmem_cache_node          219KB        220KB
kmem_cache               181KB        226KB
Out of memory and no killable processes...
Kernel panic - not syncing: System is deadlocked on memory
CPU: 0 UID: 0 PID: 5149 Comm: udevd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 vpanic+0x552/0x970 kernel/panic.c:651
 panic+0xd1/0xe0 kernel/panic.c:788
 out_of_memory.cold+0xa2/0x170 mm/oom_kill.c:1166
 __alloc_pages_may_oom mm/page_alloc.c:4116 [inline]
 __alloc_pages_slowpath mm/page_alloc.c:4967 [inline]
 __alloc_frozen_pages_noprof+0x24c2/0x2dc0 mm/page_alloc.c:5317
 alloc_pages_mpol+0x1fb/0x540 mm/mempolicy.c:2490
 alloc_pages_noprof mm/mempolicy.c:2581 [inline]
 folio_alloc_noprof+0x22/0x250 mm/mempolicy.c:2591
 filemap_alloc_folio_noprof.part.0+0x377/0x450 mm/filemap.c:1013
 filemap_alloc_folio_noprof mm/filemap.c:2027 [inline]
 __filemap_get_folio_mpol+0x653/0x1320 mm/filemap.c:2012
 __filemap_get_folio include/linux/pagemap.h:761 [inline]
 filemap_fault+0x879/0x3130 mm/filemap.c:3592
 __do_fault+0x10b/0x440 mm/memory.c:5425
 do_read_fault mm/memory.c:5860 [inline]
 do_fault+0xa99/0x1750 mm/memory.c:5994
 do_pte_missing mm/memory.c:4566 [inline]
 handle_pte_fault mm/memory.c:6379 [inline]
 __handle_mm_fault+0x187d/0x2a00 mm/memory.c:6517
 handle_mm_fault+0x37b/0xa30 mm/memory.c:6686
 do_user_addr_fault+0x5a3/0x12f0 arch/x86/mm/fault.c:1343
 handle_page_fault arch/x86/mm/fault.c:1483 [inline]
 exc_page_fault+0x6f/0xd0 arch/x86/mm/fault.c:1536
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
RIP: 0033:0x7f72d08a7407
Code: Unable to access opcode bytes at 0x7f72d08a73dd.
RSP: 002b:00007ffff9fa8a10 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 00007f72d1003880 RCX: 00007f72d08a7407
RDX: 0000000000000008 RSI: 00007ffff9fa8b70 RDI: 000000000000000b
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000bb8 R11: 0000000000000202 R12: 0000000000000000
R13: 0000558259d38100 R14: 0000000000000001 R15: 00007ffff9fa8c60
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.