From: Sohil Mehta <sohil.mehta@intel.com>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>, <x86@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"Andy Lutomirski" <luto@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra" <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/x86: Update map_shadow_stack syscall nr
Date: Fri, 1 Sep 2023 12:33:28 -0700 [thread overview]
Message-ID: <e2ae1d89-9abf-338e-e56a-dc4be19b9bfc@intel.com> (raw)
In-Reply-To: <20230901181652.2583861-1-rick.p.edgecombe@intel.com>
Hi Rick,
On 9/1/2023 11:16 AM, Rick Edgecombe wrote:
> Shadow stack's selftest utilizes the map_shadow_stack syscall. The
> syscall is new with the feature, but the selftests cannot automatically
> find the headers for the kernel source tree they are located in. This
> resulted in the shadow stack test failing to build until the brand new
> headers were installed.
>
I am wondering why a definition for __NR_map_shadow_stack is missing in
include/uapi/asm-generic/unistd.h?
Wouldn't this mean that even if someone were to install the headers they
still wouldn't get the syscall number definition. Am I missing something?
> To avoid this, a copy of the new uapi defines needed by the test were
> included in the selftest (see link for discussion). When shadow stack was
> merged the syscall number was changed, but the copy in the selftest was
> not updated.
>
> So update the copy of the syscall number define used when the required
> headers are not installed, to have the final syscall number from the
> merge.
>
How about adding a fixes tag to make it a tiny bit easier for someone
who backports the shstk series?
Fixes: 81f30337ef4f ("selftests/x86: Add shadow stack test")
> Link: https://lore.kernel.org/lkml/Y%2FijdXoTAATt0+Ct@zn.tnic/
> Signed-off-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
> ---
> tools/testing/selftests/x86/test_shadow_stack.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/x86/test_shadow_stack.c b/tools/testing/selftests/x86/test_shadow_stack.c
> index 2188968674cb..757e6527f67e 100644
> --- a/tools/testing/selftests/x86/test_shadow_stack.c
> +++ b/tools/testing/selftests/x86/test_shadow_stack.c
> @@ -40,7 +40,7 @@
> * without building the headers.
> */
> #ifndef __NR_map_shadow_stack
> -#define __NR_map_shadow_stack 452
> +#define __NR_map_shadow_stack 453
>
> #define SHADOW_STACK_SET_TOKEN (1ULL << 0)
>
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
Apart from this patch, I think we also need something like commit
78252deb023c ("arch: Register fchmodat2, usually as syscall 452") to
reserve the 453 syscall number for the rest of the architectures.
Should I send one out if you don't have something prepared already?
Thanks,
Sohil
next prev parent reply other threads:[~2023-09-01 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:16 [PATCH] selftests/x86: Update map_shadow_stack syscall nr Rick Edgecombe
2023-09-01 19:33 ` Sohil Mehta [this message]
2023-09-01 20:35 ` Edgecombe, Rick P
2023-09-01 22:19 ` Sohil Mehta
2023-09-01 22:51 ` Edgecombe, Rick P
2023-09-02 0:12 ` Sohil Mehta
2023-09-01 21:39 ` [tip: x86/urgent] " tip-bot2 for Rick Edgecombe
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=e2ae1d89-9abf-338e-e56a-dc4be19b9bfc@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--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