From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>,
amit.kachhap@arm.com, ardb@kernel.org, broonie@kernel.org
Subject: Re: [PATCH v2 0/2] arm64: pointer auth cleanup
Date: Tue, 31 Jan 2023 16:29:34 +0000 [thread overview]
Message-ID: <167518256578.583390.3074674907697424552.b4-ty@arm.com> (raw)
In-Reply-To: <20230131105809.991288-1-mark.rutland@arm.com>
On Tue, 31 Jan 2023 10:58:07 +0000, Mark Rutland wrote:
> With the recent dynamic SCS patches conditionally disabling pointer
> authentication for leaf functions, I thought I'd try to clean things up
> and consistently do so.
>
> Patch 1 is (hopefully not controversial) Makefile cleanup.
>
> Patch 2 disables pointer authentication for leaf functions, for the
> reasons laid out in the commit message (which laregly boils down to
> "it's not necessary" and "our prior rationale for doing so doesn't hold
> water").
>
> [...]
Applied to arm64 (for-next/ptrauth), thanks!
[1/2] arm64: unify asm-arch manipulation
https://git.kernel.org/arm64/c/1e249c41ea43
[2/2] arm64: pauth: don't sign leaf functions
https://git.kernel.org/arm64/c/c68cf5285e18
--
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:[~2023-01-31 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 10:58 [PATCH v2 0/2] arm64: pointer auth cleanup Mark Rutland
2023-01-31 10:58 ` [PATCH v2 1/2] arm64: unify asm-arch manipulation Mark Rutland
2023-01-31 10:58 ` [PATCH v2 2/2] arm64: pauth: don't sign leaf functions Mark Rutland
2023-01-31 16:29 ` 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=167518256578.583390.3074674907697424552.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=amit.kachhap@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@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 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.