From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Yury Khrustalev <yury.khrustalev@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, Kevin Brodsky <kevin.brodsky@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Sandipan Das <sandipan@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, x86@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org, nd@arm.com
Subject: Re: [RESEND v4 0/3] mm/pkey: Add PKEY_UNRESTRICTED macro
Date: Wed, 12 Feb 2025 13:29:06 -0800 [thread overview]
Message-ID: <20250212132906.fdf85ea62b3672cfc1115c09@linux-foundation.org> (raw)
In-Reply-To: <Z6zZanGRGd15770_@arm.com>
On Wed, 12 Feb 2025 17:24:58 +0000 Catalin Marinas <catalin.marinas@arm.com> wrote:
> On Mon, Jan 13, 2025 at 05:06:16PM +0000, Yury Khrustalev wrote:
> > Add PKEY_UNRESTRICTED macro to mman.h and use it in selftests.
> >
> > For context, this change will also allow for more consistent update of the
> > Glibc manual which in turn will help with introducing memory protection
> > keys on AArch64 targets.
> [...]
> > Yury Khrustalev (3):
> > mm/pkey: Add PKEY_UNRESTRICTED macro
> > selftests/mm: Use PKEY_UNRESTRICTED macro
> > selftests/powerpc: Use PKEY_UNRESTRICTED macro
> >
> > include/uapi/asm-generic/mman-common.h | 1 +
> > tools/testing/selftests/mm/mseal_test.c | 6 +++---
> > tools/testing/selftests/mm/pkey-helpers.h | 3 ++-
> > tools/testing/selftests/mm/pkey_sighandler_tests.c | 4 ++--
> > tools/testing/selftests/mm/protection_keys.c | 2 +-
> > tools/testing/selftests/powerpc/include/pkeys.h | 2 +-
> > tools/testing/selftests/powerpc/mm/pkey_exec_prot.c | 2 +-
> > tools/testing/selftests/powerpc/mm/pkey_siginfo.c | 2 +-
> > tools/testing/selftests/powerpc/ptrace/core-pkey.c | 6 +++---
> > tools/testing/selftests/powerpc/ptrace/ptrace-pkey.c | 6 +++---
> > 10 files changed, 18 insertions(+), 16 deletions(-)
>
> Andrew, Arnd - are you ok if I take these patches through the arm64
> tree?
Sure.
next prev parent reply other threads:[~2025-02-12 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 17:06 [RESEND v4 0/3] mm/pkey: Add PKEY_UNRESTRICTED macro Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 1/3] " Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 2/3] selftests/mm: Use " Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 3/3] selftests/powerpc: " Yury Khrustalev
2025-02-12 17:24 ` [RESEND v4 0/3] mm/pkey: Add " Catalin Marinas
2025-02-12 21:29 ` Andrew Morton [this message]
2025-02-17 21:33 ` Catalin Marinas
2025-02-18 9:56 ` Yury Khrustalev
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 9:47 Yury Khrustalev
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=20250212132906.fdf85ea62b3672cfc1115c09@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nd@arm.com \
--cc=sandipan@linux.ibm.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).