public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, amit.kachhap@arm.com,
	ardb@kernel.org, catalin.marinas@arm.com, will@kernel.org
Subject: Re: [PATCH 2/2] arm64: pauth: don't sign leaf functions
Date: Mon, 30 Jan 2023 18:33:42 +0000	[thread overview]
Message-ID: <Y9gNhmrxl6BigajH@sirena.org.uk> (raw)
In-Reply-To: <20230125182201.800076-3-mark.rutland@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 344 bytes --]

On Wed, Jan 25, 2023 at 06:22:01PM +0000, Mark Rutland wrote:

> Currently, when CONFIG_ARM64_PTR_AUTH_KERNEL=y (and
> CONFIG_UNWIND_PATCH_PAC_INTO_SCS=n), we enable pointer authentication
> for all functions, including leaf functions. This isn't necessary, and
> is unfortunate for a few reasons:

Reviewed-by: Mark Brown <broonie@kernel.org>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

      parent reply	other threads:[~2023-01-30 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 18:21 [PATCH 0/2] arm64: pointer auth cleanup Mark Rutland
2023-01-25 18:22 ` [PATCH 1/2] arm64: unify asm-arch manipulation Mark Rutland
2023-01-26  8:31   ` Ard Biesheuvel
2023-01-30 18:31   ` Mark Brown
2023-01-25 18:22 ` [PATCH 2/2] arm64: pauth: don't sign leaf functions Mark Rutland
2023-01-26  8:40   ` Ard Biesheuvel
2023-01-26 11:00     ` Mark Rutland
2023-01-30 18:33   ` Mark Brown [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=Y9gNhmrxl6BigajH@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=amit.kachhap@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox