Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc6
Date: Fri, 1 Nov 2024 11:22:08 +0000	[thread overview]
Message-ID: <20241101112207.GA8472@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc6. The important one is a change to
the way in which we handle protection keys around signal delivery so that
we're more closely aligned with the x86 behaviour, however there is also
a revert of the previous fix to disable software tag-based KASAN with
GCC, since a workaround materialised shortly afterwards.

I'd love to say we're done with 6.12, but we're aware of some longstanding
fpsimd register corruption issues that we're almost at the bottom of
resolving. Hopefully we'll be done reviewing the fixes next week, so
there'll be one more pull from me before the merge window opens.

Cheers,

Will

--->8

The following changes since commit 7aed6a2c51ffc97a126e0ea0c270fab7af97ae18:

  kasan: Disable Software Tag-Based KASAN with GCC (2024-10-15 11:38:10 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 2e8a1acea8597ff42189ea94f0a63fa58640223d:

  arm64: signal: Improve POR_EL0 handling to avoid uaccess failures (2024-10-29 17:59:12 +0000)

----------------------------------------------------------------
arm64 fixes for -rc6

- Fix handling of POR_EL0 during signal delivery so that pushing the
  signal context doesn't fail based on the pkey configuration of the
  interrupted context and align our user-visible behaviour with that of
  x86.

- Fix a bogus pointer being passed to the CPU hotplug code from the
  Arm SDEI driver.

- Re-enable software tag-based KASAN with GCC by using an alternative
  implementation of '__no_sanitize_address'.

----------------------------------------------------------------
Kevin Brodsky (1):
      arm64: signal: Improve POR_EL0 handling to avoid uaccess failures

Marco Elver (2):
      kasan: Fix Software Tag-Based KASAN with GCC
      Revert "kasan: Disable Software Tag-Based KASAN with GCC"

Xiongfeng Wang (1):
      firmware: arm_sdei: Fix the input parameter of cpuhp_remove_state()

 arch/arm64/kernel/signal.c   | 92 +++++++++++++++++++++++++++++++++++++-------
 drivers/firmware/arm_sdei.c  |  2 +-
 include/linux/compiler-gcc.h |  4 ++
 lib/Kconfig.kasan            |  7 +---
 4 files changed, 85 insertions(+), 20 deletions(-)


             reply	other threads:[~2024-11-01 11:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 11:22 Will Deacon [this message]
2024-11-01 18:34 ` [GIT PULL] arm64 fixes for -rc6 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-11-11 18:07 Will Deacon
2025-11-11 19:10 ` pr-tracker-bot
2025-07-09 15:08 Will Deacon
2025-07-09 18:37 ` pr-tracker-bot
2024-06-28  8:59 Will Deacon
2024-06-28 17:01 ` pr-tracker-bot
2024-02-23 10:25 Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2021-12-15 11:19 Will Deacon
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 18:49   ` Linus Torvalds
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-09  0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-12  9:14   ` Will Deacon
2017-04-12 10:18     ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 Will Deacon

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=20241101112207.GA8472@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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