From: Marc Zyngier <maz@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, joey.gouly@arm.com,
suzuki.poulose@arm.com, stable-commits@vger.kernel.org
Subject: Re: Patch "KVM: arm64: Discard PC update state on vcpu reset" has been added to the 5.15-stable tree
Date: Mon, 30 Mar 2026 11:44:01 +0100 [thread overview]
Message-ID: <87a4vpd2by.wl-maz@kernel.org> (raw)
In-Reply-To: <2026033051-fidelity-outdated-3211@gregkh>
On Mon, 30 Mar 2026 10:22:23 +0100,
Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, Mar 30, 2026 at 09:31:16AM +0100, Marc Zyngier wrote:
> > On Sun, 29 Mar 2026 13:48:18 +0100,
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > >
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > KVM: arm64: Discard PC update state on vcpu reset
> > >
> > > to the 5.15-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > kvm-arm64-discard-pc-update-state-on-vcpu-reset.patch
> > > and it can be found in the queue-5.15 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> >
> > This won't even compile, as the helpers required were only added in
> > 6.0.
>
> Ah, then the "Fixes:" tag was wrong here :(
I think the tag is correct. That's the point where the bug was
introduced, but that doesn't mean the fix applies all the way back.
Fixes for pre-6.0 will be pretty different, I expect.
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
prev parent reply other threads:[~2026-03-30 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026032918-porthole-overshoot-bef3@gregkh>
2026-03-30 8:31 ` Patch "KVM: arm64: Discard PC update state on vcpu reset" has been added to the 5.15-stable tree Marc Zyngier
2026-03-30 9:22 ` Greg KH
2026-03-30 10:44 ` Marc Zyngier [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=87a4vpd2by.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joey.gouly@arm.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
/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