From: Vasant Hegde <vasant.hegde@amd.com>
To: <tglx@linutronix.de>, <linux-kernel@vger.kernel.org>
Cc: <x86@kernel.org>, <dave.hansen@linux.intel.com>, <bp@alien8.de>,
<mingo@redhat.com>, Vasant Hegde <vasant.hegde@amd.com>,
"Dheeraj Kumar Srivastava" <dheerajkumar.srivastava@amd.com>
Subject: [PATCH] x86/smp: Validate APIC ID before parking CPU in INIT
Date: Wed, 19 Jul 2023 05:13:02 +0000 [thread overview]
Message-ID: <20230719051302.15801-1-vasant.hegde@amd.com> (raw)
Below commit is causing kexec to hang in certain scenarios with >255 CPUs.
Reproduce steps:
- We are using 2 socket system with 384 CPUs
- Booting first kernel with kernel command line intremap=off
This disabled x2apic in kernel and booted with apic mode
- During kexec it tries to send INIT to all CPUs except boot CPU
If APIC ID is 0x100 (like in our case) then it will send CPU0
to INIT mode and system hangs (in APIC mode DEST field is 8bit)
Fix this issue by adding apic->apic_id_valid() check before sending
INIT sequence.
Fixes: 45e34c8af58f ("x86/smp: Put CPUs into INIT on shutdown if possible")
Reported-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
Tested-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
---
arch/x86/kernel/smpboot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index e1aa2cd7734b..e5ca0689c4dd 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1360,7 +1360,7 @@ bool smp_park_other_cpus_in_init(void)
if (cpu == this_cpu)
continue;
apicid = apic->cpu_present_to_apicid(cpu);
- if (apicid == BAD_APICID)
+ if (apicid == BAD_APICID || !apic->apic_id_valid(apicid))
continue;
send_init_sequence(apicid);
}
--
2.31.1
next reply other threads:[~2023-07-19 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 5:13 Vasant Hegde [this message]
2023-08-03 16:28 ` [PATCH] x86/smp: Validate APIC ID before parking CPU in INIT Vasant Hegde
2023-08-09 18:42 ` Thomas Gleixner
2023-08-09 18:52 ` Thomas Gleixner
2023-08-10 11:26 ` Vasant Hegde
2023-09-04 8:27 ` Vasant Hegde
2023-09-04 13:48 ` [tip: x86/urgent] x86/smp: Don't send INIT to non-present and non-booted CPUs tip-bot2 for Thomas Gleixner
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=20230719051302.15801-1-vasant.hegde@amd.com \
--to=vasant.hegde@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dheerajkumar.srivastava@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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