[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240725205537.GA858788@bhelgaas>
Date: Thu, 25 Jul 2024 15:55:37 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Lizhi Hou <lizhi.hou@....com>, Rob Herring <robh@...nel.org>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
kvm-ppc@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Saravana Kannan <saravanak@...gle.com>,
Vaibhav Jain <vaibhav@...ux.ibm.com>,
Nicholas Piggin <npiggin@...il.com>,
Michael Ellerman <mpe@...erman.id.au>,
Vaidyanathan Srinivasan <svaidy@...ux.ibm.com>,
Kowshik Jois B S <kowsjois@...ux.ibm.com>,
Lukas Wunner <lukas@...ner.de>
Subject: Re: [PATCH v2] PCI: Fix crash during pci_dev hot-unplug on pseries
KVM guest
On Thu, Jul 25, 2024 at 11:15:39PM +0530, Amit Machhiwal wrote:
> ...
> The crash in question is a critical issue that we would want to have
> a fix for soon. And while this is still being figured out, is it
> okay to go with the fix I proposed in the V1 of this patch?
v6.10 has been released already, and it will be a couple months before
the v6.11 release.
It looks like the regression is 407d1a51921e, which appeared in v6.6,
almost a year ago, so it's fairly old.
What target are you thinking about for the V1 patch? I guess if we
add it as a v6.11 post-merge window fix, it might get backported to
stable kernels before v6.11? But if the plan is to merge the V1 patch
and then polish it again before v6.11 releases, I'm not sure it's
worth the churn.
Bjorn
Powered by blists - more mailing lists