From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Dmitry Vyukov <dvyukov@google.com>,
peterz@infradead.org, boqun.feng@gmail.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, aruna.ramakrishna@oracle.com, elver@google.com
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/4] x86/signal: Use write_permissive_pkey_val() helper
Date: Mon, 24 Feb 2025 14:11:08 -0500 [thread overview]
Message-ID: <9bc9896a-b0a3-41f4-9a51-dc0b0eb49f5c@efficios.com> (raw)
In-Reply-To: <85372b646f6d316e38578632cb4678f8ce724b95.1740403209.git.dvyukov@google.com>
On 2025-02-24 08:20, Dmitry Vyukov wrote:
> Use the new switch_to_permissive_pkey_reg() helper instead of the
> custom code. No functional changes intended.
>
> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> 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: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
> Cc: x86@kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> ---
> Changes in v3:
> - restore sig_prepare_pkru with the large comment and
> make it call the new write_permissive_pkey_val
> ---
> arch/x86/kernel/signal.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kernel/signal.c b/arch/x86/kernel/signal.c
> index 5f441039b5725..27a66a0697dd2 100644
> --- a/arch/x86/kernel/signal.c
> +++ b/arch/x86/kernel/signal.c
> @@ -28,6 +28,7 @@
> #include <linux/entry-common.h>
> #include <linux/syscalls.h>
> #include <linux/rseq.h>
> +#include <linux/pkeys.h>
>
> #include <asm/processor.h>
> #include <asm/ucontext.h>
> @@ -72,10 +73,7 @@ static inline int is_x32_frame(struct ksignal *ksig)
> */
> static inline u32 sig_prepare_pkru(void)
> {
> - u32 orig_pkru = read_pkru();
> -
> - write_pkru(0);
> - return orig_pkru;
> + return write_permissive_pkey_val();
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Note that I would be curious to see if we could get away with changing
this to enable_zero_pkey_val() without breaking any real-life user.
AFAIU this would remove a WRPKRU from signal delivery, but would require
the signal frames to be pkey-0, which is technically be a new ABI
constraint never expressed before.
Thanks,
Mathieu
> }
>
> /*
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-02-24 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1740403209.git.dvyukov@google.com>
2025-02-24 13:20 ` [PATCH v4 1/4] pkeys: add API to switch to permissive/zero pkey register Dmitry Vyukov
2025-02-24 19:04 ` Mathieu Desnoyers
2025-02-25 13:54 ` Dmitry Vyukov
2025-02-24 13:20 ` [PATCH v4 2/4] x86/signal: Use write_permissive_pkey_val() helper Dmitry Vyukov
2025-02-24 19:11 ` Mathieu Desnoyers [this message]
2025-02-24 13:20 ` [PATCH v4 3/4] rseq: Make rseq work with protection keys Dmitry Vyukov
2025-02-24 19:18 ` Mathieu Desnoyers
2025-02-25 14:07 ` Dmitry Vyukov
2025-02-25 14:28 ` Mathieu Desnoyers
2025-02-25 14:51 ` Dmitry Vyukov
2025-02-25 14:53 ` Mathieu Desnoyers
2025-02-27 14:03 ` Dmitry Vyukov
2025-02-24 13:20 ` [PATCH v4 4/4] selftests/rseq: Add test for rseq+pkeys Dmitry Vyukov
2025-02-24 19:48 ` Mathieu Desnoyers
2025-02-25 13:55 ` Dmitry Vyukov
2025-02-24 13:28 ` [PATCH v4 0/4] rseq: Make rseq work with protection keys Dmitry Vyukov
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=9bc9896a-b0a3-41f4-9a51-dc0b0eb49f5c@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®