From: Catalin Marinas <catalin.marinas@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Will Deacon <will@kernel.org>,
dave.martin@arm.com, keescook@chromium.org
Subject: Re: (subset) [PATCH v4 0/2] arm64: Support Enhanced PAN
Date: Fri, 26 Mar 2021 11:05:54 +0000 [thread overview]
Message-ID: <161675674368.29458.15003738954717175881.b4-ty@arm.com> (raw)
In-Reply-To: <20210312173811.58284-1-vladimir.murzin@arm.com>
On Fri, 12 Mar 2021 17:38:09 +0000, Vladimir Murzin wrote:
> ARM architecture gains support of Enhanced Privileged Access Never
> (EPAN) which allows Privileged Access Never to be used with
> Execute-only mappings.
>
> As a consequence 24cecc377463 ("arm64: Revert support for execute-only
> user mappings") can be revisited and re-enabled.
>
> [...]
Applied to arm64 (for-next/epan), thanks!
[1/2] arm64: Support execute-only permissions with Enhanced PAN
https://git.kernel.org/arm64/c/18107f8a2df6
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-26 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 17:38 [PATCH v4 0/2] arm64: Support Enhanced PAN Vladimir Murzin
2021-03-12 17:38 ` [PATCH v4 1/2] arm64: Support execute-only permissions with " Vladimir Murzin
2021-03-25 19:06 ` Will Deacon
2021-03-26 11:04 ` Catalin Marinas
2021-03-30 8:47 ` Geert Uytterhoeven
2021-03-30 9:30 ` Catalin Marinas
2021-03-30 9:34 ` Geert Uytterhoeven
2021-03-12 17:38 ` [PATCH v4 2/2] arm64: Introduce HWCAPS2_EXECONLY Vladimir Murzin
2021-03-25 19:00 ` Will Deacon
2021-03-26 9:35 ` Catalin Marinas
2021-03-29 8:53 ` Will Deacon
2021-03-26 11:05 ` Catalin Marinas [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=161675674368.29458.15003738954717175881.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=dave.martin@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vladimir.murzin@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).