From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"jackm@mellanox.com" <jackm@mellanox.com>,
KY Srinivasan <kys@microsoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
"Adrian Suhov (Cloudbase Solutions SRL)" <v-adsuho@microsoft.com>,
"Chris Valean (Cloudbase Solutions SRL)" <v-chvale@microsoft.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
Josh Poulson <jopoulso@microsoft.com>
Subject: Re: FAILED: patch "[PATCH] PCI: hv: Serialize the present and eject work items" failed to apply to 4.9-stable tree
Date: Sun, 22 Apr 2018 16:02:31 +0200 [thread overview]
Message-ID: <20180422140231.GA28177@kroah.com> (raw)
In-Reply-To: <KL1P15301MB0006F1F194147748A60AE1B4BF8A0@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
On Sun, Apr 22, 2018 at 01:49:55PM +0000, Dexuan Cui wrote:
> > From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>
> > Sent: Sunday, April 22, 2018 02:45
> > On Tue, Apr 17, 2018 at 02:06:01AM +0000, Dexuan Cui wrote:
> > > > From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > > Sent: Monday, April 16, 2018 06:23
> > > >
> > > > Dexuan,
> > > >
> > > > On Mon, Apr 16, 2018 at 12:15:06PM +0200, gregkh@linuxfoundation.org
> > > > wrote:
> > > > >
> > > > > The patch below does not apply to the 4.9-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>.
> > > >
> > > > Please do as Greg asks in order to complete the stable backport you
> > > > have requested.
> > > >
> > > > Lorenzo
> > > >
> > > > > greg k-h
> > >
> > > Hi Greg, Lorenzo,
> > > It turns out that Hyper-V vPCI driver (drivers/pci/host/pci-hyperv.c) in v4.9.y
> > > is broken on latest Hyper-V hosts, because it lacks more fixes, e.g. at least
> > > we must cherry-pick these 2 extra fixes:
> > > 7dcf90e PCI: hv: Use vPCI protocol version 1.2
> > > b1db7e7 PCI: hv: Add vPCI version protocol negotiation
> > >
> > > Otherwise, we always get a "hv_pci ... Request for interrupt failed:
> > 0xc0350005"
> > > error, as reported in
> > https://github.com/Microsoft/azure-linux-kernel/issues/13
> > >
> > > The 2 extra fixes depend on a few more patches, and a manual resolution of
> > > conflicts is required...
> > >
> > > Backporting all the required patches to v4.9 seems too many. IMO we may
> > as
> > > well simply drop this patch ("PCI: hv: Serialize the present and eject work
> > items")
> > > for v4.9 and 4.10, 4.11 and 4.12, which are all broken due to the same
> > reason.
> > >
> > > I can confirm this patch ("PCI: hv: Serialize the present and eject work
> > items")
> > > can be applied cleanly to v4.13+.
> > >
> > > PS, For Hyper-V users that want PCIe-pass-through and NIC SR-IOV on some
> > > certain versions of kernels, they can pick the patches here:
> > >
> > https://github.com/Microsoft/azure-linux-kernel
> This link is just FYI only. I didn't mean to ask you to pick any patch from it. :-)
>
> > I'm sorry, I'm still totally confused.
> >
> > What exact git commit ids do you wish to see applied to which stable
> > tree?
> I hope this mainline patch
> 021ad274d7dc ("PCI: hv: Serialize the present and eject work items")
> can be cherry-pick'd to v4.13.y.
4.13.y has been end-of-life for a very long time now. So there's
nothing I can do there.
> I have verified this patch is already in v4.14.y, v4.15.y and v4.16.y, and
> it can be cleanly applied to v4.13.y.
That's because 4.13.y is end-of-life and has not gotten an update for a
very long time.
So there's nothing for me to do now? Great! :)
greg k-h
next prev parent reply other threads:[~2018-04-22 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 10:15 FAILED: patch "[PATCH] PCI: hv: Serialize the present and eject work items" failed to apply to 4.9-stable tree gregkh
2018-04-16 13:22 ` Lorenzo Pieralisi
2018-04-17 2:06 ` Dexuan Cui
2018-04-22 9:45 ` gregkh
2018-04-22 13:49 ` Dexuan Cui
2018-04-22 14:02 ` gregkh [this message]
2018-04-23 5:11 ` Dexuan Cui
2018-04-23 23:43 ` Dexuan Cui
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=20180422140231.GA28177@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Michael.H.Kelley@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jackm@mellanox.com \
--cc=jopoulso@microsoft.com \
--cc=kys@microsoft.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=v-adsuho@microsoft.com \
--cc=v-chvale@microsoft.com \
--cc=vkuznets@redhat.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.