linux-kernel - Kernel panic - not syncing: System is deadlocked on memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJNGr6ve_6o6drwe_+bRW6UU4Ew9EjaZYaBgx0JAQjYb+A8VSA@mail.gmail.com>
Date: Sun, 11 May 2025 19:35:14 +0800
From: Yin Guoyu <y04609127@...il.com>
To: akpm@...ux-foundation.org, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org
Subject: Kernel panic - not syncing: System is deadlocked on memory

Hi,
When I test the Linux kernel (commit
38fec10eb60d687e30c8c6b5420d86e8149f7557), I encountered a kernel
panic issue related to memory allocation, specifically in the
alloc_pages_mpol function. The panic message indicates "System is
deadlocked on memory," and the call trace points to
__alloc_frozen_pages_noprof failing to allocate pages, leading to an
OOM condition.
The error originates in alloc_pages_mpol, which calls policy_nodemask
to determine the nodemask and nid for memory allocation. The
subsequent call to __alloc_frozen_pages_noprof fails when the system
runs out of memory, with no swap available and no killable processes.
This crash can be triggered by executing the provided C reproducer
multiple times. The reproducer performs a series of system calls
(e.g., file creation, perf_event_open, io_submit, and filesystem
mounts), which likely stress the memory management system and expose
the bug.
This can be reproduced on:
HEAD commit:
38fec10eb60d687e30c8c6b5420d86e8149f7557
console output : https://pastebin.com/raw/T4dfWHSf
kernel config : https://pastebin.com/raw/u0Efyj5P
C reproducer : https://pastebin.com/raw/3hPqjF6M