From: Alex Williamson <alex.williamson@redhat.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Greg KH <greg@kroah.com>, stable@vger.kernel.org
Subject: Re: Please apply commit cf0d53ba4947 and 523184972b28 to v4.4.y, v4.9.y, v4.14.y
Date: Fri, 20 Apr 2018 15:50:37 -0600 [thread overview]
Message-ID: <20180420155037.5c7ad1ef@w520.home> (raw)
In-Reply-To: <517631f5-494e-b91f-109a-94fca05715c8@codeaurora.org>
On Fri, 20 Apr 2018 17:06:42 -0400
Sinan Kaya <okaya@codeaurora.org> wrote:
> Hi Greg,
>
> On 4/20/2018 12:47 PM, Sinan Kaya wrote:
> > I'll take a look at 4.4.y and check with Alex if these can be backported or not.
> >
>
> I worked with Alex today.
>
> The commit 523184972b28 doesn't apply because of another missing patch on 4.4.y
> kernel.
>
> commit ddf9dc0eb531 ("vfio-pci: Virtualize PCIe & AF FLR")
>
> Please apply commit ddf9dc0eb531 ("vfio-pci: Virtualize PCIe & AF FLR") before applying
> 523184972b28.
>
> commit ddf9dc0eb531 ("vfio-pci: Virtualize PCIe & AF FLR") also fixes a real issue
> as follows:
>
> "This seems to fix several instance of devices getting into bad states
> with userspace drivers, like dpdk, running inside a VM."
>
>
> It would be good to pull both to 4.y.
>
> I'll have to work on cf0d53ba4947 next.
cf0d53ba4947 should be a clean pick to latest 4.4.y, after applying
ddf9dc0eb531 followed by 523184972b28, at least that's the way it
worked for me. The additional commit ddf9dc0eb531 made the v4.9
release, so it's already present in the other stable trees. Thanks,
Alex
next prev parent reply other threads:[~2018-04-20 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 17:07 Please apply commit cf0d53ba4947 and 523184972b28 to v4.4.y, v4.9.y, v4.14.y Sinan Kaya
2018-04-19 17:21 ` Alex Williamson
2018-04-20 6:55 ` Greg KH
2018-04-20 16:47 ` Sinan Kaya
2018-04-20 16:56 ` Greg KH
2018-04-20 21:06 ` Sinan Kaya
2018-04-20 21:50 ` Alex Williamson [this message]
2018-04-22 7:20 ` Greg KH
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=20180420155037.5c7ad1ef@w520.home \
--to=alex.williamson@redhat.com \
--cc=greg@kroah.com \
--cc=okaya@codeaurora.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).