From: Xianying Wang <wangxianying546@gmail.com>
To: akpm@linux-foundation.org
Cc: vbabka@suse.cz, surenb@google.com, mhocko@suse.com,
jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [BUG] WARNING in __alloc_frozen_pages_noprof
Date: Wed, 19 Nov 2025 17:07:02 +0800 [thread overview]
Message-ID: <CAOU40uAHO9-59HB2VmCBfC5OiNg3BZBd-32jphtRd-nkvhD6Dg@mail.gmail.com> (raw)
Hi,
I hit the following warning in the page allocator when opening a perf
event with callchain sampling after increasing
kernel.perf_event_max_stack.This warning can be triggered by first
writing a large value into kernel.perf_event_max_stack and then
opening a perf event with callchain sampling enabled.
The reproducer does two things:
1) It writes a large (but still accepted) value to the sysctl:
echo 0x40132 > /proc/sys/kernel/perf_event_max_stack
(0x40132 = 262450 in decimal. This is below the current upper bound
enforced by perf_event_max_stack_handler(), which uses 640 * 1024
as extra2.)
2) It calls perf_event_open() with callchain sampling:
struct perf_event_attr attr = {
.type = PERF_TYPE_HARDWARE,
.size = sizeof(attr),
.config = PERF_COUNT_HW_CPU_CYCLES,
.sample_type = PERF_SAMPLE_CALLCHAIN,
.sample_period = 1,
.disabled = 1,
};
fd = syscall(__NR_perf_event_open, &attr, -1, 0, -1, 0);
The same warning is reproducible on both v6.17.0 and v6.18-rc2
(6.18.0-rc2-00120 g6fab32bb6508), only the line numbers in
__alloc_frozen_pages_noprof() differ slightly.
The suspected cause is that alloc_callchain_buffers() uses
sysctl_perf_event_max_stack directly when computing the size of the
per-CPU callchain buffers. For large but valid values of
kernel.perf_event_max_stack, perf_callchain_entry__sizeof() grows to
several megabytes, and alloc_callchain_buffers() ends up doing a very
large contiguous kmalloc_node() per CPU. This high-order allocation
then triggers the warning in __alloc_frozen_pages_noprof() in the page
allocator.
This can be reproduced on:
HEAD commit:
e5f0a698b34ed76002dc5cff3804a61c80233a7a
6fab32bb6508abbb8b7b1c5498e44f0c32320ed5
report: https://pastebin.com/raw/bCq3d4KR
console output : https://pastebin.com/raw/5hfk57Vd
kernel config : https://pastebin.com/raw/1grwrT16
C reproducer :https://pastebin.com/raw/GADWbwKN
Let me know if you need more details or testing.
Best regards,
Xianying
next reply other threads:[~2025-11-19 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:07 Xianying Wang [this message]
2025-11-26 9:46 ` Vlastimil Babka
2025-11-26 11:19 ` Peter Zijlstra
2025-11-26 19:00 ` Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOU40uAHO9-59HB2VmCBfC5OiNg3BZBd-32jphtRd-nkvhD6Dg@mail.gmail.com \
--to=wangxianying546@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox