From: Marc Zyngier <maz@kernel.org>
To: "Gowans, James" <jgowans@amazon.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"yuzenghui@huawei.com" <yuzenghui@huawei.com>,
"chenxiang66@hisilicon.com" <chenxiang66@hisilicon.com>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Sironi, Filippo" <sironi@amazon.de>
Subject: Re: FAILED: patch "[PATCH] KVM: arm64: vgic-v4: Make the doorbell request robust w.r.t" failed to apply to 5.10-stable tree
Date: Tue, 02 Jul 2024 09:36:20 +0100 [thread overview]
Message-ID: <867ce4i41n.wl-maz@kernel.org> (raw)
In-Reply-To: <62f253b96773478773a6cc79977663a687e0f8eb.camel@amazon.com>
On Mon, 01 Jul 2024 11:56:57 +0100,
"Gowans, James" <jgowans@amazon.com> wrote:
>
> On Sun, 2023-07-23 at 22:41 +0200, gregkh@linuxfoundation.org wrote:
> > The patch below does not apply to the 5.10-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> Blast from the past, but we've recently been bitten by this bug when
> running a v5.10 kernel. I'm going to back-port it to v5.10 and v5.15,
> resolve the conflicts and post it.
>
> Marc, please will you take a look and see if you're happy with the
> backport? The main change is going back to the old style of vCPU flag
> manipulation.
Thanks for having a stab at this.
I eyeballed the two patches, and couldn't see anything untoward.
However, I haven't tested them, as life is too short to run
prehistoric kernels ;-).
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-07-02 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 20:41 FAILED: patch "[PATCH] KVM: arm64: vgic-v4: Make the doorbell request robust w.r.t" failed to apply to 5.10-stable tree gregkh
2024-07-01 10:56 ` Gowans, James
2024-07-02 8:36 ` Marc Zyngier [this message]
2024-07-01 10:57 ` [PATCH 5.10.y] KVM: arm64: vgic-v4: Make the doorbell request robust w.r.t preemption James Gowans
2024-07-02 8:42 ` Marc Zyngier
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=867ce4i41n.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=chenxiang66@hisilicon.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgowans@amazon.com \
--cc=oliver.upton@linux.dev \
--cc=sironi@amazon.de \
--cc=stable@vger.kernel.org \
--cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.