mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "bill.roberts@arm.com" <bill.roberts@arm.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"tglx@kernel.org" <tglx@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>, "bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86/shstk: shadow stack enabling write return code change
Date: Tue, 7 Jul 2026 18:56:50 +0000	[thread overview]
Message-ID: <b0dd13550ccc34e34714f7d73f7be67a2b6bbe84.camel@intel.com> (raw)
In-Reply-To: <20260707184542.1721085-1-bill.roberts@arm.com>

On Tue, 2026-07-07 at 13:45 -0500, Bill Roberts wrote:
> The WRSS instruction (the special instruction that writes to shadow stacks)
> cannot be used in userspace unless IA32_U_CET.SH_STK_EN=1 (user shadow
> stack is enabled). So the kernel *should* return -EINVAL to userspace if
> it tries to enable it when shadow stack is disabled. However, currently,
> it will return -EPERM. But, that error code doesn't fit the condition as
> the failure is due to an invalid state change request not a permission
> issue.
> 
> Investigating userspace call sites, like glibc and criu (checkpoint code),
> they do not rely on this specific error message, nor could a userspace
> effectively utilize this specific return error code to indicate a
> difference in "I cannot enable write because of invalid permissions"
> versus "I cannot enable write because the shadow stack is disabled".
> 
> Signed-off-by: Bill Roberts <bill.roberts@arm.com>

Reviewed-by: Rick Edgecombe <rick.p.edgecombe@intel.com>

> ---
>  arch/x86/kernel/shstk.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/shstk.c b/arch/x86/kernel/shstk.c
> index 0ca64900192f..eb690ba90180 100644
> --- a/arch/x86/kernel/shstk.c
> +++ b/arch/x86/kernel/shstk.c
> @@ -490,7 +490,7 @@ static int wrss_control(bool enable)
>  	 * when disabling.
>  	 */
>  	if (!features_enabled(ARCH_SHSTK_SHSTK))
> -		return -EPERM;
> +		return -EINVAL;
>  
>  	/* Already enabled/disabled? */
>  	if (features_enabled(ARCH_SHSTK_WRSS) == enable)


  reply	other threads:[~2026-07-07 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 18:45 Bill Roberts
2026-07-07 18:56 ` Edgecombe, Rick P [this message]
2026-07-08 16:46 ` Dave Hansen
2026-07-08 20:56   ` Bill Roberts
2026-07-08 21:00     ` Dave Hansen
2026-07-14 20:22       ` Bill Roberts
2026-07-14 20:27         ` Dave Hansen
2026-09-02 21:11 ` [tip: x86/cpu] x86/shstk: Shadow " tip-bot2 for Bill Roberts

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=b0dd13550ccc34e34714f7d73f7be67a2b6bbe84.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=bill.roberts@arm.com \
    --cc=bp@alien8.de \
    --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

all inboxes | Powered by JetHome®