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 -rc8/final
Date: Fri, 20 May 2022 12:52:51 +0100 [thread overview]
Message-ID: <20220520115250.GA6700@willie-the-truck> (raw)
Hi Linus,
Please pull these three arm64 fixes for -rc8/final. The MTE and stolen
time fixes have been doing the rounds for a little while, but review
and testing feedback was ongoing until earlier this week. The kexec fix
showed up on Monday and addresses a failure observed under Qemu.
Summary in the tag. Cheers,
Will
--->8
The following changes since commit 51f559d66527e238f9a5f82027bff499784d4eac:
arm64: Enable repeat tlbi workaround on KRYO4XX gold CPUs (2022-05-12 13:15:38 +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 1d0cb4c8864addc362bae98e8ffa5500c87e1227:
arm64: mte: Ensure the cleared tags are visible before setting the PTE (2022-05-17 14:29:51 +0100)
----------------------------------------------------------------
arm64 fixes for -rc8/final
- Add missing write barrier to publish MTE tags before a pte update
- Fix kexec relocation clobbering its own data structures
- Fix stolen time crash if a timer IRQ fires during CPU hotplug
----------------------------------------------------------------
Catalin Marinas (1):
arm64: mte: Ensure the cleared tags are visible before setting the PTE
Mark Rutland (1):
arm64: kexec: load from kimage prior to clobbering
Prakruthi Deepak Heragu (1):
arm64: paravirt: Use RCU read locks to guard stolen_time
arch/arm64/kernel/mte.c | 3 +++
arch/arm64/kernel/paravirt.c | 29 +++++++++++++++++++++--------
arch/arm64/kernel/relocate_kernel.S | 22 +++++++++++++++-------
3 files changed, 39 insertions(+), 15 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-20 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 11:52 Will Deacon [this message]
2022-05-20 18:36 ` [GIT PULL] arm64 fixes for -rc8/final pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-07-31 12:31 Will Deacon
2020-07-31 16:45 ` pr-tracker-bot
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=20220520115250.GA6700@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;
as well as URLs for NNTP newsgroup(s).