From: Bill Roberts <bill.roberts@arm.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"shuah@kernel.org" <shuah@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@kernel.org" <tglx@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] selftest/x86: test ARCH_SHSTK_UNLOCK
Date: Wed, 9 Sep 2026 15:25:24 -0500 [thread overview]
Message-ID: <19ee1440-e140-4f1e-bc39-9d2cccfa9c78@arm.com> (raw)
In-Reply-To: <440cdd41a203589b31e287378de146e18e620176.camel@intel.com>
On 8/27/26 6:32 PM, Edgecombe, Rick P wrote:
> On Tue, 2026-07-07 at 14:11 -0500, Bill Roberts wrote:
>> Test that ARCH_SHSTK_UNLOCK can't be called from normal (non-ptrace)
>> context.
>>
>> Signed-off-by: Bill Roberts <bill.roberts@arm.com>
>> ---
> Reviewed-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
Bump, I don't see these acked/staged anywhere.
Links in case you need the patches handy:
1.
https://lore.kernel.org/all/d223c3e24650c3d29f162bb7faaac74ccb7bf65a.camel@intel.com/
2.
https://lore.kernel.org/all/440cdd41a203589b31e287378de146e18e620176.camel@intel.com/
prev parent reply other threads:[~2026-09-09 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 19:11 [PATCH v2 1/2] arch/x86: handle ARCH_SHSTK_ENABLE explicitly Bill Roberts
2026-07-07 19:11 ` [PATCH v2 2/2] selftest/x86: test ARCH_SHSTK_UNLOCK Bill Roberts
2026-08-27 23:32 ` Edgecombe, Rick P
2026-09-09 18:47 ` Bill Roberts
2026-09-09 18:58 ` Edgecombe, Rick P
2026-09-09 20:25 ` 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=19ee1440-e140-4f1e-bc39-9d2cccfa9c78@arm.com \
--to=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=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.