From: Catalin Marinas <catalin.marinas@arm.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Kevin Brodsky <kevin.brodsky@arm.com>,
linux-arm-kernel@lists.infradead.org,
dave.hansen@linux.intel.com, yury.khrustalev@arm.com,
will@kernel.org, linux-kselftest@vger.kernel.org,
Aishwarya TCV <aishwarya.tcv@arm.com>
Subject: Re: [PATCH] selftests/mm: Define PKEY_UNRESTRICTED for pkey_sighandler_tests
Date: Thu, 7 Nov 2024 21:34:26 +0000 [thread overview]
Message-ID: <Zy0yYo5feyJx1Y6D@arm.com> (raw)
In-Reply-To: <50f87b47-e326-4e87-a1d4-cc24ea70f432@linuxfoundation.org>
On Thu, Nov 07, 2024 at 02:26:11PM -0700, Shuah Khan wrote:
> On 11/7/24 11:00, Catalin Marinas wrote:
> > On Thu, Nov 07, 2024 at 09:50:20AM -0700, Shuah Khan wrote:
> > > On 11/7/24 06:16, Kevin Brodsky wrote:
> > > > Commit 6e182dc9f268 ("selftests/mm: Use generic pkey register
> > > > manipulation") makes use of PKEY_UNRESTRICTED in
> > > > pkey_sighandler_tests. The macro has been proposed for addition to
> > > > uapi headers [1], but the patch hasn't landed yet.
> > > >
> > > > Define PKEY_UNRESTRICTED in pkey-helpers.h for the time being to fix
> > > > the build.
> > >
> > > What does mean to say "time being" - can this be removed in the
> > > future. If so please add a FIXME so this define can be removed
> > > later.
> >
> > There's a dependency on this series:
> >
> > https://lore.kernel.org/r/20241028090715.509527-2-yury.khrustalev@arm.com/
> >
> > Which I did not notice. Typically the uapi patches are picked by Arnd
> > but first that series needs to be reposted with the comments addressed.
> >
> > I think for now we either merge this fix from Kevin (happy to add a
> > FIXME comment when applying), change the kselftest to use 0 instead of
> > PKEY_UNRESTRICTED or revert the top two patches here:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/pkey-signal
> >
> > I'm fine with all options really, it's not essential that we get the
> > kselftest patches above merged in 6.13.
>
> I am good with taking this patch as is with a FIXME to cleanup
> later.
Thanks Shuah.
--
Catalin
next prev parent reply other threads:[~2024-11-07 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 13:16 [PATCH] selftests/mm: Define PKEY_UNRESTRICTED for pkey_sighandler_tests Kevin Brodsky
2024-11-07 16:50 ` Shuah Khan
2024-11-07 18:00 ` Catalin Marinas
2024-11-07 21:26 ` Shuah Khan
2024-11-07 21:34 ` Catalin Marinas [this message]
2024-11-08 11:07 ` Catalin Marinas
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=Zy0yYo5feyJx1Y6D@arm.com \
--to=catalin.marinas@arm.com \
--cc=aishwarya.tcv@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=will@kernel.org \
--cc=yury.khrustalev@arm.com \
/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