From: Andrei Vagin <avagin@google.com>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
"Chang S. Bae" <chang.seok.bae@intel.com>
Cc: linux-kernel@vger.kernel.org, criu@lists.linux.dev,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Andrei Vagin <avagin@google.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH v2 0/4] x86/fpu: Restore and reinforce signal frame portability
Date: Thu, 4 Jun 2026 16:56:00 +0000 [thread overview]
Message-ID: <20260604165604.1195243-1-avagin@google.com> (raw)
The x86 signal frame is designed to be self-describing. The xstate_size
field in the software-reserved bytes indicates the actual size of the
xstate context and is used by the kernel to locate the FP_XSTATE_MAGIC2
marker during signal return.
This design is required to provide portability of signal frames across
different machines. For example, a process checkpointed on a system with
fewer xstate features and restored on a system with more features will
have a signal frame on its stack that is smaller than the destination
host's default. By relying on the frame's internal xstate_size, the
kernel can correctly validate and restore such frames.
This series addresses a regression introduced in commit dc8aa31a7ac2
("x86/fpu: Refine and simplify the magic number check during signal
return").
v2: Address sashiko comments.
44eeff9bc467 ("Revert "x86/fpu: Refine and simplify the magic number
check during signal return"") has been merged.
Cc: Thomas Gleixner <tglx@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>
Andrei Vagin (5):
Revert "x86/fpu: Refine and simplify the magic number check during
signal return"
x86/fpu: Document signal frame portability
selftests/x86: Add a test for signal frame portability
x86/fpu: Add consistency check between xstate_size and xfeatures
selftests/x86: Add a consistency test for signal frames
Documentation/arch/x86/xstate.rst | 14 +-
arch/x86/include/uapi/asm/sigcontext.h | 10 +
arch/x86/kernel/fpu/signal.c | 29 ++-
arch/x86/kernel/fpu/xstate.c | 2 +-
arch/x86/kernel/fpu/xstate.h | 2 +
tools/testing/selftests/x86/Makefile | 5 +-
.../selftests/x86/sigframe_portability.c | 205 ++++++++++++++++++
tools/testing/selftests/x86/xstate.c | 5 -
tools/testing/selftests/x86/xstate.h | 12 +
9 files changed, 269 insertions(+), 15 deletions(-)
create mode 100644 tools/testing/selftests/x86/sigframe_portability.c
--
2.54.0.746.g67dd491aae-goog
next reply other threads:[~2026-06-04 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 16:56 Andrei Vagin [this message]
2026-06-04 16:56 ` [PATCH 1/4] x86/fpu: Document signal frame portability Andrei Vagin
2026-06-04 22:32 ` Andrei Vagin
2026-06-04 16:56 ` [PATCH 2/4] selftests/x86: Add a test for " Andrei Vagin
2026-06-04 16:56 ` [PATCH 3/4] x86/fpu: Add consistency check between xstate_size and xfeatures Andrei Vagin
2026-06-05 9:50 ` Ingo Molnar
2026-06-04 16:56 ` [PATCH 4/4] selftests/x86: Add a consistency test for signal frames Andrei Vagin
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=20260604165604.1195243-1-avagin@google.com \
--to=avagin@google.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=criu@lists.linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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