From: Sasha Levin <sashal@kernel.org>
To: Matthew Rosato <mjrosato@linux.ibm.com>
Cc: stable@vger.kernel.org, alex.williamson@redhat.com, cohuck@redhat.com
Subject: Re: [PATCH] Request backport of a vfio patch for 5.4 stable
Date: Wed, 13 Jan 2021 12:51:20 -0500 [thread overview]
Message-ID: <20210113175120.GU4035784@sasha-vm> (raw)
In-Reply-To: <1610386288-26220-1-git-send-email-mjrosato@linux.ibm.com>
On Mon, Jan 11, 2021 at 12:31:27PM -0500, Matthew Rosato wrote:
>Upstream commit 7d6e1329652e ("vfio iommu: Add dma available capability")
>should probably have been identified as a stable candidate originally, as
>without this available in a KVM host QEMU guests on at least s390x can
>end up with broken PCI passthrough devices, as the guest is unaware of the
>vfio DMA limit and can easily overrun it.
>
>The commit in question won't fit cleanly to 5.4, so I've included a
>proposed backport patch.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2021-01-13 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 17:31 [PATCH] Request backport of a vfio patch for 5.4 stable Matthew Rosato
2021-01-11 17:31 ` [PATCH] vfio iommu: Add dma available capability Matthew Rosato
2021-01-13 17:51 ` Sasha Levin [this message]
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=20210113175120.GU4035784@sasha-vm \
--to=sashal@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=mjrosato@linux.ibm.com \
--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