From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 6.13-rc3
Date: Fri, 13 Dec 2024 17:41:38 +0000 [thread overview]
Message-ID: <Z1xx0ha7lbKkdhRC@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit fac04efc5c793dccbd07e2d59af9f90b7fc0dca4:
Linux 6.13-rc2 (2024-12-08 14:03:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to ce03573a1917532da06057da9f8e74a2ee9e2ac9:
kselftest/arm64: abi: fix SVCR detection (2024-12-13 14:59:37 +0000)
----------------------------------------------------------------
arm64 fixes for 6.13-rc3:
- arm64 stacktrace: address some fallout from the recent changes to
unwinding across exception boundaries
- Ensure the arm64 signal delivery failure is recoverable - only
override the return registers after all the user accesses took place
- Fix the arm64 kselftest access to SVCR - only when SME is detected
----------------------------------------------------------------
Kevin Brodsky (1):
arm64: signal: Ensure signal delivery failure is recoverable
Mark Rutland (2):
arm64: stacktrace: Skip reporting LR at exception boundaries
arm64: stacktrace: Don't WARN when unwinding other tasks
Weizhao Ouyang (1):
kselftest/arm64: abi: fix SVCR detection
arch/arm64/kernel/signal.c | 48 +++++++++++++++-------
arch/arm64/kernel/stacktrace.c | 32 ++++-----------
.../testing/selftests/arm64/abi/syscall-abi-asm.S | 32 +++++++--------
3 files changed, 55 insertions(+), 57 deletions(-)
--
Catalin
next reply other threads:[~2024-12-13 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 17:41 Catalin Marinas [this message]
2024-12-13 22:34 ` [GIT PULL] arm64 fixes for 6.13-rc3 pr-tracker-bot
2024-12-15 17:06 ` Sasha Levin
2024-12-16 10:02 ` Mark Rutland
2024-12-16 14:59 ` Sasha Levin
2024-12-16 17:36 ` Mark Rutland
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=Z1xx0ha7lbKkdhRC@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).