* [PATCH] lib/smp_processor_id: Don't warn if there is only one CPU
@ 2026-11-11 9:24 Huacai Chen
2026-11-11 17:06 ` Peter Zijlstra
0 siblings, 1 reply; 2+ messages in thread
From: Huacai Chen @ 2026-11-11 9:24 UTC (permalink / raw)
To: Andrew Morton, Ingo Molnar, Peter Zijlstra, Juri Lelli,
Vincent Guittot, Dietmar Eggemann, Steven Rostedt, Ben Segall,
Mel Gorman, Huacai Chen
Cc: linux-mm, linux-kernel, Huacai Chen, stable, Tiezhu Yang
When CONFIG_DEBUG_PREEMPT is enabled on a Non-SMP (single-core) kernel,
calls to smp_processor_id() in preemptible contexts trigger some false
positive "BUG: using smp_processor_id() in preemptible" warnings, which
are harmless noise because the process always executes on CPU 0 and CPU
migration is impossible.
Here are some of the trimmed log messages:
Call Trace:
[<9000000000d33e28>] show_stack+0xf8/0x1c0
[<9000000000d2fdac>] dump_stack_lvl+0x4c/0x78
[<9000000002456fc0>] check_preemption_disabled.isra.0+0x100/0x110
[<9000000002456ff8>] debug_smp_processor_id+0x18/0x40
[<9000000000d31118>] init_cache_level+0x18/0x90
[<9000000001adbe2c>] detect_cache_attributes+0x4c/0x640
[<9000000001adc44c>] cacheinfo_cpu_online+0x1c/0x310
[<9000000000d5ae04>] cpuhp_issue_call.constprop.0+0x94/0xd0
[<9000000000d5b278>] __cpuhp_setup_state_cpuslocked+0x208/0x320
[<9000000000d30148>] do_one_initcall+0x68/0x200
[<90000000024711b8>] kernel_init_freeable+0x1fc/0x294
[<900000000245824c>] kernel_init+0x20/0x134
[<9000000002455b54>] ret_from_kernel_thread+0x24/0x1d0
[<9000000000d31650>] ret_from_kernel_thread_asm+0xc/0x9c
This warning only exists for the !CONFIG_SMP build. This is because for
CONFIG_SMP cpuhp_issue_call() invokes callbacks in cpuhp_thread_fun()
which is a percpu thread, but for !CONFIG_SMP build it invoke callbacks
in the init process which is not a percpu thread. And there is such a
skip condition in check_preemption_disabled():
if (is_percpu_thread())
goto out;
Since there is only one CPU for the !CONFIG_SMP, we can simply skip the
warning if (nr_cpu_ids == 1) in check_preemption_disabled().
Cc: stable@vger.kernel.org
Reported-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
---
lib/smp_processor_id.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/smp_processor_id.c b/lib/smp_processor_id.c
index 94b3f6b19538..64901d33c0ee 100644
--- a/lib/smp_processor_id.c
+++ b/lib/smp_processor_id.c
@@ -19,6 +19,9 @@ unsigned int check_preemption_disabled(const char *what1, const char *what2)
if (irqs_disabled())
goto out;
+ if (nr_cpu_ids == 1)
+ goto out;
+
if (is_percpu_thread())
goto out;
--
2.52.0
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] lib/smp_processor_id: Don't warn if there is only one CPU
2026-11-11 9:24 [PATCH] lib/smp_processor_id: Don't warn if there is only one CPU Huacai Chen
@ 2026-11-11 17:06 ` Peter Zijlstra
0 siblings, 0 replies; 2+ messages in thread
From: Peter Zijlstra @ 2026-11-11 17:06 UTC (permalink / raw)
To: Huacai Chen
Cc: Andrew Morton, Ingo Molnar, Juri Lelli, Vincent Guittot,
Dietmar Eggemann, Steven Rostedt, Ben Segall, Mel Gorman,
Huacai Chen, linux-mm, linux-kernel, stable, Tiezhu Yang
On Wed, Nov 11, 2026 at 05:24:21PM +0800, Huacai Chen wrote:
> When CONFIG_DEBUG_PREEMPT is enabled on a Non-SMP (single-core) kernel,
> calls to smp_processor_id() in preemptible contexts trigger some false
> positive "BUG: using smp_processor_id() in preemptible" warnings, which
> are harmless noise because the process always executes on CPU 0 and CPU
> migration is impossible.
The check is still valid, you don't want to have any code that uses
smp_processor_id() outside of preempt_disable(). Such code would be
invalid on SMP, even when ran on UP.
All code must be SMP ready.
Aside from that, nr_cpu_ids is the wrong number to check.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-11 17:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-11 9:24 [PATCH] lib/smp_processor_id: Don't warn if there is only one CPU Huacai Chen
2026-11-11 17:06 ` Peter Zijlstra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®