From: Bill Roberts <bill.roberts@arm.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"pjw@kernel.org" <pjw@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"mingo@redhat.com" <mingo@redhat.com>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"shuah@kernel.org" <shuah@kernel.org>,
"tglx@kernel.org" <tglx@kernel.org>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH 2/2] selftests/x86: add generic prctl shadow stack test
Date: Mon, 3 Aug 2026 12:50:16 -0500 [thread overview]
Message-ID: <a5c308ea-bcb2-4911-ac07-d493d08a5f21@arm.com> (raw)
In-Reply-To: <5c04899f405619f0bdde1f98e432e382f76a686b.camel@intel.com>
On 7/29/26 8:31 AM, Edgecombe, Rick P wrote:
> On Tue, 2026-07-14 at 10:47 -0500, Bill Roberts wrote:
>> diff --git a/tools/testing/selftests/x86/test_shadow_stack_prctl.c
>> b/tools/testing/selftests/x86/test_shadow_stack_prctl.c
>> new file mode 100644
>> index 000000000000..9c9e2728a9f9
>> --- /dev/null
>> +++ b/tools/testing/selftests/x86/test_shadow_stack_prctl.c
>> @@ -0,0 +1,3 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +#define BUILD_PRCTL 1
>> +#include "test_shadow_stack.c"
>> --
> Hmm, do we really need a full re-test for the different prctl routing?
Bear with me, I am quite perplexed, usually tests are meant with fanfare.
Yes we want this! It ensures all regressions are caught and features are
working
as intended through both interfaces. This means, nothing broke for x86
in this change.
Tests are cheap, I have no idea why we wouldn't want this.
Now, what I did want to propose in the future, is moving a generic test
up out of
arch specific tests that would run on all systems. This will require me
to look at all
3 arches and build a test suite. However, I wanted to ensure that
nothing broke for x86,
this ensures that. I was going to roll those patches after the LSM
changes go up.
As an aside and hearkening back to your comment on UNLOCK in patch 1,
the test never tests UNLOCK.
prev parent reply other threads:[~2026-08-03 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 15:47 [PATCH 0/2] x86: Support shstk via prctl Bill Roberts
2026-07-14 15:47 ` [PATCH 1/2] x86/shstk: support " Bill Roberts
2026-07-29 13:29 ` Edgecombe, Rick P
2026-08-03 17:41 ` Bill Roberts
2026-08-03 18:14 ` Edgecombe, Rick P
2026-08-04 18:23 ` Bill Roberts
2026-08-04 18:49 ` Edgecombe, Rick P
2026-08-04 20:43 ` Bill Roberts
2026-08-04 21:59 ` Edgecombe, Rick P
2026-08-05 17:16 ` Bill Roberts
2026-07-14 15:47 ` [PATCH 2/2] selftests/x86: add generic prctl shadow stack test Bill Roberts
2026-07-29 13:31 ` Edgecombe, Rick P
2026-08-03 17:50 ` Bill Roberts [this message]
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=a5c308ea-bcb2-4911-ac07-d493d08a5f21@arm.com \
--to=bill.roberts@arm.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=shuah@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 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®