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 -rc5
Date: Sun, 11 Sep 2022 12:37:27 +0100	[thread overview]
Message-ID: <20220911113725.GA2070@willie-the-truck> (raw)

Hi Linus,

When you get a moment, please can you pull these three small arm64 fixes?
They're all related to optional architecture extensions: BTI, SME and
52-bit virtual addressing.

Summary in the tag.

Cheers,

Will

--->8

The following changes since commit 5fbc49cef91916140a305f22f7430e9a7ea0c6b4:

  arm64: mm: Reserve enough pages for the initial ID map (2022-09-01 12:02:39 +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 3fe3fd5f30720b4afd3345cc186808125e7f5848:

  arm64: mm: fix resume for 52-bit enabled builds (2022-09-10 14:46:28 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Disable in-kernel BTI when compiling with GCC, as it makes invalid
  assumptions about the distance between functions which has led to
  crashes when calling modules on a CPU with BTI support.

- Remove bogus TIF_SME flag management if memory allocation fails in the
  ptrace code.

- Fix the resume path when configured for 52-bit virtual addressing.

----------------------------------------------------------------
Joey Gouly (1):
      arm64: mm: fix resume for 52-bit enabled builds

Mark Brown (2):
      arm64/bti: Disable in kernel BTI when cross section thunks are broken
      arm64/ptrace: Don't clear calling process' TIF_SME on OOM

 arch/arm64/Kconfig         | 2 ++
 arch/arm64/kernel/ptrace.c | 2 --
 arch/arm64/kernel/sleep.S  | 3 +++
 3 files changed, 5 insertions(+), 2 deletions(-)

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

             reply	other threads:[~2022-09-11 11:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 11:37 Will Deacon [this message]
2022-09-11 19:36 ` [GIT PULL] arm64 fixes for -rc5 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-07-24 16:26 Will Deacon
2026-07-24 19:23 ` pr-tracker-bot
2026-03-20 13:06 Will Deacon
2026-03-20 16:25 ` pr-tracker-bot
2025-03-01 21:21 Will Deacon
2025-03-01 21:48 ` pr-tracker-bot
2024-02-16 11:58 Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2023-10-06  7:56 Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-09 10:52   ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-04-12 16:05 [GIT PULL] arm64 " Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-02  1:00 ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2017-03-31 17:15 Will Deacon
2016-06-24 11:41 Will Deacon
2016-02-19 16:29 Will Deacon
2015-10-07 14:20 Will Deacon
2015-01-16 17:16 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=20220911113725.GA2070@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