From: Paul Sherman <shermanpauldylan@gmail.com>
To: linux-riscv@lists.infradead.org
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, Paul Sherman <shermanpauldylan@gmail.com>
Subject: [PATCH v2] riscv: smp: set CPU 0 possible in setup_smp()
Date: Tue, 14 Jul 2026 15:33:01 -0700 [thread overview]
Message-ID: <20260714223301.5265-1-shermanpauldylan@gmail.com> (raw)
setup_smp() calls set_cpu_possible() for CPUs 1..nr_cpu_ids-1 but
never for CPU 0 (the boot CPU). x86 handles this via
init_cpu_possible(cpumask_of(0)); RISC-V has no equivalent.
Without CPU 0 in cpu_possible_mask, rcu_init_one()'s
for_each_possible_cpu() loop skips it, leaving rdp->mynode=NULL.
rcutree_prepare_cpu() then dereferences NULL and hangs.
Exposed on Sophgo SG2042 (64-hart, 4-NUMA) with Linux 7.2-rc3.
Fixes: a4166aec1130 ("riscv: Deduplicate code in setup_smp()")
Signed-off-by: Paul Sherman <shermanpauldylan@gmail.com>
---
arch/riscv/kernel/smpboot.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/riscv/kernel/smpboot.c b/arch/riscv/kernel/smpboot.c
index f6ef57930b50..8d3a437c0f30 100644
--- a/arch/riscv/kernel/smpboot.c
+++ b/arch/riscv/kernel/smpboot.c
@@ -171,6 +171,15 @@ void __init setup_smp(void)
for (cpuid = 1; cpuid < nr_cpu_ids; cpuid++)
if (cpuid_to_hartid_map(cpuid) != INVALID_HARTID)
set_cpu_possible(cpuid, true);
+
+ /*
+ * Boot CPU (cpuid=0) is never set possible by the loop above.
+ * x86 and arm64 call init_cpu_possible(cpumask_of(0)) explicitly;
+ * RISC-V was missing this. Without it, rcu_init_one()'s
+ * for_each_possible_cpu loop skips CPU 0, leaving rdp->mynode=NULL,
+ * causing rcutree_prepare_cpu() to dereference NULL and hang.
+ */
+ set_cpu_possible(0, true);
}
static int start_secondary_cpu(int cpu, struct task_struct *tidle)
--
2.53.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2026-07-14 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 22:33 Paul Sherman [this message]
2026-07-15 1:41 ` [PATCH v2] riscv: smp: set CPU 0 possible in setup_smp() Paul Walmsley
2026-07-15 4:01 ` Vivian Wang
2026-07-15 4:51 ` Paul Sherman
2026-07-15 6:20 ` Vivian Wang
2026-07-15 14:14 ` Paul Walmsley
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=20260714223301.5265-1-shermanpauldylan@gmail.com \
--to=shermanpauldylan@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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