From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Amit Daniel Kachhap <amit.kachhap@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
catalin.marinas@arm.com, Mark Brown <broonie@kernel.org>,
James Morse <james.morse@arm.com>,
Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
kernel-team@android.com, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH v8 0/6] arm64: add Armv8.3 pointer authentication enhancements
Date: Mon, 14 Sep 2020 13:16:57 +0100 [thread overview]
Message-ID: <160008162341.3660775.7794909078874111646.b4-ty@kernel.org> (raw)
In-Reply-To: <20200914083656.21428-1-amit.kachhap@arm.com>
On Mon, 14 Sep 2020 14:06:50 +0530, Amit Daniel Kachhap wrote:
> These patch series adds support for Armv8.3 pointer authentication
> enhanced features mandatory for Armv8.6 and optional for Armv8.3.
> These features are,
>
> * Enhanced PAC generation algorithm (ARMv8.3-pauth2).
> * Generate fault when authenticate instruction fails (ARMV8.3-FPAC).
>
> [...]
Applied to arm64 (for-next/ptrauth), thanks!
[1/6] arm64: kprobe: add checks for ARMv8.3-PAuth combined instructions
https://git.kernel.org/arm64/c/93396936ed0c
[2/6] arm64: traps: Allow force_signal_inject to pass esr error code
https://git.kernel.org/arm64/c/4ef333b2d106
[3/6] arm64: ptrauth: Introduce Armv8.3 pointer authentication enhancements
https://git.kernel.org/arm64/c/e16aeb072682
[4/6] arm64: cpufeature: Modify address authentication cpufeature to exact
https://git.kernel.org/arm64/c/ba9d1d3e3e7c
[5/6] arm64: kprobe: disable probe of fault prone ptrauth instruction
https://git.kernel.org/arm64/c/6560edca515e
[6/6] arm64: kprobe: clarify the comment of steppable hint instructions
https://git.kernel.org/arm64/c/03c9c8fad6cb
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
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:[~2020-09-14 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:36 [PATCH v8 0/6] arm64: add Armv8.3 pointer authentication enhancements Amit Daniel Kachhap
2020-09-14 8:36 ` [PATCH v8 1/6] arm64: kprobe: add checks for ARMv8.3-PAuth combined instructions Amit Daniel Kachhap
2020-09-14 8:36 ` [PATCH v8 2/6] arm64: traps: Allow force_signal_inject to pass esr error code Amit Daniel Kachhap
2020-09-14 8:36 ` [PATCH v8 3/6] arm64: ptrauth: Introduce Armv8.3 pointer authentication enhancements Amit Daniel Kachhap
2020-09-14 8:36 ` [PATCH v8 4/6] arm64: cpufeature: Modify address authentication cpufeature to exact Amit Daniel Kachhap
2020-09-14 10:22 ` Catalin Marinas
2020-09-14 8:36 ` [PATCH v8 5/6] arm64: kprobe: disable probe of fault prone ptrauth instruction Amit Daniel Kachhap
2020-09-14 8:36 ` [PATCH v8 6/6] arm64: kprobe: clarify the comment of steppable hint instructions Amit Daniel Kachhap
2020-09-14 12:16 ` Will Deacon [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=160008162341.3660775.7794909078874111646.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=Vincenzo.Frascino@arm.com \
--cc=amit.kachhap@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@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