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 -rc3
Date: Fri, 20 Jun 2025 11:50:06 +0100 [thread overview]
Message-ID: <20250620105005.GA22615@willie-the-truck> (raw)
Hi Linus,
Please pull these four arm64 fixes for -rc3. There's nothing major (even
the vmalloc one is just suppressing a potential warning) but all worth
having, nonetheless.
Cheers,
Will
--->8
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
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 39dfc971e42d886e7df01371cd1bef505076d84c:
arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() (2025-06-12 17:28:18 +0100)
----------------------------------------------------------------
arm64 fixes for -rc3
- Suppress KASAN false positive in stack unwinding code.
- Drop redundant reset of the GCS state on exec().
- Don't try to descend into a !present PMD when creating a huge vmap()
entry at the PUD level.
- Fix a small typo in the arm64 booting Documentation.
----------------------------------------------------------------
Dev Jain (1):
arm64: Restrict pagetable teardown to avoid false warning
Lorenzo Pieralisi (1):
docs: arm64: Fix ICC_SRE_EL2 register typo in booting.rst
Mark Brown (1):
arm64/gcs: Don't call gcs_free() during flush_gcs()
Tengda Wu (1):
arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth()
Documentation/arch/arm64/booting.rst | 2 +-
arch/arm64/kernel/process.c | 4 +++-
arch/arm64/kernel/ptrace.c | 2 +-
arch/arm64/mm/mmu.c | 3 ++-
4 files changed, 7 insertions(+), 4 deletions(-)
next reply other threads:[~2025-06-20 11:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:50 Will Deacon [this message]
2025-06-20 17:29 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 22:49 Will Deacon
2026-03-07 4:34 ` pr-tracker-bot
2025-02-14 14:04 Will Deacon
2025-02-14 19:29 ` pr-tracker-bot
2024-06-07 11:30 Will Deacon
2024-06-07 22:07 ` pr-tracker-bot
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22 0:07 ` Linus Torvalds
2020-02-22 0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31 4:25 ` pr-tracker-bot
2019-01-20 0:04 Will Deacon
2019-01-20 3:29 ` Linus Torvalds
2019-01-20 4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 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=20250620105005.GA22615@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