From: Sasha Levin <sashal@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, criu@lists.linux.dev,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Andrei Vagin <avagin@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/5] Revert "x86/fpu: Refine and simplify the magic number check during signal return"
Date: Wed, 27 May 2026 15:48:58 -0400 [thread overview]
Message-ID: <20260527-agent5-item004-x86fpu@kernel.org> (raw)
In-Reply-To: <20260526205047.3339490-2-avagin@google.com>
> This reverts commit dc8aa31a7ac2 ("x86/fpu: Refine and simplify the
> magic number check during signal return").
>
> The reverted commit broke applications that construct signal frames in
> userspace (such as CRIU and gVisor) if the frame's xstate size is
> smaller than the kernel's fpstate->user_size.
Holding this off on the stable side until the revert (and the rest of
the series) lands in mainline. Once it's upstream, please ping with the
mainline SHAs and the list of trees you want it on, and I'll queue it.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-05-27 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 20:50 [PATCH 0/5] x86/fpu: Restore and reinforce signal frame portability Andrei Vagin
2026-05-26 20:50 ` [PATCH 1/5] Revert "x86/fpu: Refine and simplify the magic number check during signal return" Andrei Vagin
2026-05-27 19:48 ` Sasha Levin [this message]
2026-05-28 17:08 ` Andrei Vagin
2026-06-03 15:13 ` Sasha Levin
2026-05-26 20:50 ` [PATCH 2/5] x86/fpu: Document signal frame portability Andrei Vagin
2026-05-26 20:50 ` [PATCH 3/5] selftests/x86: Add a test for " Andrei Vagin
2026-05-26 20:50 ` [PATCH 4/5] x86/fpu: Add consistency check between xstate_size and xfeatures Andrei Vagin
2026-05-26 20:50 ` [PATCH 5/5] 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=20260527-agent5-item004-x86fpu@kernel.org \
--to=sashal@kernel.org \
--cc=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=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.