From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com ([66.111.4.27]:45153 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752618AbeDTQ42 (ORCPT ); Fri, 20 Apr 2018 12:56:28 -0400 Date: Fri, 20 Apr 2018 18:56:21 +0200 From: Greg KH To: Sinan Kaya Cc: stable@vger.kernel.org, Alex Williamson Subject: Re: Please apply commit cf0d53ba4947 and 523184972b28 to v4.4.y, v4.9.y, v4.14.y Message-ID: <20180420165621.GA9853@kroah.com> References: <3dc65572-74c2-4f09-1729-8957c5f36ac9@codeaurora.org> <20180420065509.GA4876@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Fri, Apr 20, 2018 at 12:47:52PM -0400, Sinan Kaya wrote: > On 4/20/2018 2:55 AM, Greg KH wrote: > > On Thu, Apr 19, 2018 at 01:07:29PM -0400, Sinan Kaya wrote: > >> Hi Greg, > >> > >> Upstream commit cf0d53ba4947 ("vfio/pci: Virtualize Maximum Read Request > >> Size") and commit 523184972b28 ("vfio/pci: Virtualize Maximum Payload Size") > >> fixes nasty PCIe virtualization issues for platforms that support Maximum > >> Payload Size bigger than 128. > >> > >> Issue shows up when a device is assigned to the guest machine as a passthrough. > >> Guest machine configures the MPS/MRRS settings to values that are incompatible > >> with the parent bridge device. > >> > >> This causes PCIe transaction timeouts and AER errors to be spilled in the host > >> kernel. > >> > >> Please apply commit cf0d53ba4947 and 523184972b28 to all affected releases to > >> fix the resulting regression. > > It looks like the commit 523184972b28 ("vfio/pci: Virtualize Maximum Payload Size") > is already applied for 4.9.94. > > Go ahead and apply commit cf0d53ba4947 ("vfio/pci: Virtualize Maximum Read Request > Size") for 4.9.y. Yes, added that to the 4.14.y and 4.9.y trees (you can't forget 4.14.y...) thanks, greg k-h