From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: stable@vger.kernel.org, catalin.marinas@arm.com, lee@kernel.org,
sdonthineni@nvidia.com, will@kernel.org
Subject: Re: [PATCH 6.18.y 0/5] arm64: errata: Mitigate TLBI errata on various Arm CPUs
Date: Tue, 16 Jun 2026 17:16:49 +0530 [thread overview]
Message-ID: <2026061641-flip-baggage-b527@gregkh> (raw)
In-Reply-To: <ajEq3rRp8rYQg7Fu@J2N7QTR9R3>
On Tue, Jun 16, 2026 at 11:52:14AM +0100, Mark Rutland wrote:
> On Tue, Jun 16, 2026 at 03:34:27PM +0530, Greg KH wrote:
> > On Tue, Jun 16, 2026 at 03:31:11PM +0530, Greg KH wrote:
> > > On Tue, Jun 16, 2026 at 06:13:24AM +0100, Mark Rutland wrote:
> > > > This is a v6.18-only backport of a workaround for a TLB invalidation
> > > > issue affecting several CPUs. The final patches landed in mainline
> > > > yesterday:
> > > >
> > > > https://lore.kernel.org/linux-arm-kernel/178157002783.358810.8206806281627742561.pr-tracker-bot@kernel.org/
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80476f22b8b7e193b26f285a7c9f9e4b63abca16
> > > >
> > > > This issue has been assigned CVE ID CVE-2025-10263, and Arm have
> > > > published a security bulletin:
> > > >
> > > > https://developer.arm.com/documentation/112137/latest/
> > > >
> > > > I've pushed a copy of this backport to my kernel.org repo:
> > > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=stable-6.18/arm-4118414/backport
> > >
> > > Should I cherry-pick these to 7.1.y and 7.0.y as well?
> >
> > Ok, cherry-picking didn't work well, I gave up on patch 3...
> >
> > Can you send backports for those branches too?
>
> Sorry about that.
>
> I'll send out backports for v7.0.y and v7.1.y later today.
Wonderful, thanks!
greg k-h
prev parent reply other threads:[~2026-06-16 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 5:13 [PATCH 6.18.y 0/5] arm64: errata: Mitigate TLBI errata on various Arm CPUs Mark Rutland
2026-06-16 5:13 ` [PATCH 6.18.y 1/5] arm64: cputype: Add C1-Ultra definitions Mark Rutland
2026-06-16 5:13 ` [PATCH 6.18.y 2/5] arm64: cputype: Add C1-Premium definitions Mark Rutland
2026-06-16 5:13 ` [PATCH 6.18.y 3/5] arm64: errata: Mitigate TLBI errata on various Arm CPUs Mark Rutland
2026-06-16 5:13 ` [PATCH 6.18.y 4/5] arm64: errata: Mitigate TLBI errata on NVIDIA Olympus CPU Mark Rutland
2026-06-16 5:13 ` [PATCH 6.18.y 5/5] arm64: errata: Mitigate TLBI errata on Microsoft Azure Cobalt 100 CPU Mark Rutland
2026-06-16 10:01 ` [PATCH 6.18.y 0/5] arm64: errata: Mitigate TLBI errata on various Arm CPUs Greg KH
2026-06-16 10:04 ` Greg KH
2026-06-16 10:52 ` Mark Rutland
2026-06-16 11:46 ` Greg KH [this message]
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=2026061641-flip-baggage-b527@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=lee@kernel.org \
--cc=mark.rutland@arm.com \
--cc=sdonthineni@nvidia.com \
--cc=stable@vger.kernel.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