From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org,
Cornelia Huck <cornelia.huck@de.ibm.com>,
marc.deslauriers@ubuntu.com
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH 0/2] virtio: fix VirtQueue->inuse field
Date: Tue, 23 Aug 2016 11:57:17 -0400 [thread overview]
Message-ID: <20160823155717.GC3948@stefanha-x1.localdomain> (raw)
In-Reply-To: <e56d6c16-261c-5b30-c422-bc25ac0aa68b@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
On Tue, Aug 23, 2016 at 08:49:35AM +0200, Peter Lieven wrote:
> Am 17.08.2016 um 15:58 schrieb Stefan Hajnoczi:
> > On Mon, Aug 15, 2016 at 01:54:14PM +0100, Stefan Hajnoczi wrote:
> > > The VirtQueue->inuse field is not always updated correctly. These patches fix
> > > it.
> > >
> > > Originally this series was called "virtio-balloon: fix stats vq migration" but
> > > Ladi Prosek posted a nicer fix called "balloon: Fix failure of updating guest
> > > memory status". I dropped the virtio-balloon patches.
> > >
> > > Changes from previous series:
> > > * Missing comma in error formatting [Fam]
> > > * virtio_descard() -> virtio_discard() [Michael]
> > > * Multi-line comment style [Cornelia]
> > >
> > > Stefan Hajnoczi (2):
> > > virtio: recalculate vq->inuse after migration
> > > virtio: decrement vq->inuse in virtqueue_discard()
> > >
> > > hw/virtio/virtio.c | 16 ++++++++++++++++
> > > 1 file changed, 16 insertions(+)
> > I should mention this is for QEMU 2.7. These fixes are needed if the
> > CVE-2016-5403 patch has been applied.
> >
> > Without these patches any device that holds VirtQueueElements across
> > live migration will terminate with a "Virtqueue size exceeded" error
> > message. virtio-balloon and virtio-scsi are affected. virtio-blk
> > probably too but I haven't tested it.
> >
> > Stefan
>
> I noticed that these patches are not in master yet and therefore
> not included in the 2.7.0-rc4 tagges yesterday. Is there any issue with them?
I think Michael Tsirkin is offline. This series is waiting on him to
merge.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-23 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 12:54 [Qemu-devel] [PATCH 0/2] virtio: fix VirtQueue->inuse field Stefan Hajnoczi
2016-08-15 12:54 ` [Qemu-devel] [PATCH 1/2] virtio: recalculate vq->inuse after migration Stefan Hajnoczi
2016-08-15 12:54 ` [Qemu-devel] [PATCH 2/2] virtio: decrement vq->inuse in virtqueue_discard() Stefan Hajnoczi
2016-08-17 13:58 ` [Qemu-devel] [PATCH 0/2] virtio: fix VirtQueue->inuse field Stefan Hajnoczi
2016-08-23 6:49 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2016-08-23 15:57 ` Stefan Hajnoczi [this message]
2016-08-22 14:00 ` [Qemu-devel] " Denis V. Lunev
2016-08-22 18:23 ` Denis V. Lunev
2016-08-30 19:54 ` Stefan Hajnoczi
2016-08-30 20:02 ` Denis V. Lunev
2016-08-31 9:25 ` Roman Kagan
2016-08-31 17:06 ` Denis V. Lunev
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=20160823155717.GC3948@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=marc.deslauriers@ubuntu.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@gmail.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 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).