All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: amit.kachhap@arm.com, ardb@kernel.org, broonie@kernel.org,
	catalin.marinas@arm.com, mark.rutland@arm.com, will@kernel.org
Subject: [PATCH v2 0/2] arm64: pointer auth cleanup
Date: Tue, 31 Jan 2023 10:58:07 +0000	[thread overview]
Message-ID: <20230131105809.991288-1-mark.rutland@arm.com> (raw)

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").

Since v1 [1]:
* Fix typos in patch 2's commit message
* Add tags from Ard and Mark

[1] https://lore.kernel.org/linux-arm-kernel/20230125182201.800076-1-mark.rutland@arm.com/

Thanks,
Mark.

Mark Rutland (2):
  arm64: unify asm-arch manipulation
  arm64: pauth: don't sign leaf functions

 arch/arm64/Kconfig  |  4 +--
 arch/arm64/Makefile | 65 ++++++++++++++++++---------------------------
 2 files changed, 28 insertions(+), 41 deletions(-)

-- 
2.30.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-01-31 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 10:58 Mark Rutland [this message]
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 ` [PATCH v2 0/2] arm64: pointer auth cleanup 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=20230131105809.991288-1-mark.rutland@arm.com \
    --to=mark.rutland@arm.com \
    --cc=amit.kachhap@arm.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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.