From: Eric Biggers <ebiggers@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-pm@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ayush Jain <Ayush.Jain3@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v3 0/2] x86/fpu: Fix irq_fpu_usable() to return false during CPU onlining
Date: Tue, 20 May 2025 08:29:36 -0700 [thread overview]
Message-ID: <20250520152938.21881-1-ebiggers@kernel.org> (raw)
This series fixes a crash in the SHA-256 code during hotplug CPU
onlining.
Changed in v3:
- Split into two patches, as requested by Ingo.
Changed in v2:
- Add WARN_ON_FPU when kernel_fpu_allowed has unexpected value in
fpu__init_cpu() or cpu_disable_common(). Since WARN_ON_FPU is
defined in fpu/internal.h which should not be included by smpboot.c,
made cpu_disable_common() call a new function fpu__disable_cpu().
- Added Tested-by.
Eric Biggers (2):
x86/fpu: Replace in_kernel_fpu with kernel_fpu_allowed
x86/fpu: Fix irq_fpu_usable() to return false during CPU onlining
arch/x86/include/asm/fpu/api.h | 1 +
arch/x86/kernel/fpu/core.c | 34 +++++++++++++++++++++-------------
arch/x86/kernel/fpu/init.c | 13 +++++++++++++
arch/x86/kernel/fpu/internal.h | 2 ++
arch/x86/kernel/smpboot.c | 6 ++++++
5 files changed, 43 insertions(+), 13 deletions(-)
base-commit: 3ee84e3dd88e39b55b534e17a7b9a181f1d46809
--
2.49.0
next reply other threads:[~2025-05-20 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 15:29 Eric Biggers [this message]
2025-05-20 15:29 ` [PATCH v3 1/2] x86/fpu: Replace in_kernel_fpu with kernel_fpu_allowed Eric Biggers
2025-05-20 15:29 ` [PATCH v3 2/2] x86/fpu: Fix irq_fpu_usable() to return false during CPU onlining Eric Biggers
2025-05-28 2:04 ` kernel test robot
2025-05-28 4:25 ` Eric Biggers
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=20250520152938.21881-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Ayush.Jain3@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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