qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL v2 0/6] virtio,pci: bugfixes
Date: Mon, 27 Jul 2020 10:31:57 -0400	[thread overview]
Message-ID: <20200727143104.97776-1-mst@redhat.com> (raw)

v2 due to issues noticed by dgilbert in v1.
Changes from v1:
    dropped a work around for pci migration for old machine types.


The following changes since commit 4215d3413272ad6d1c6c9d0234450b602e46a74c:

  Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-5.1-20200727' into staging (2020-07-27 09:33:04 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream

for you to fetch changes up to d0d89526f70ded5ac41a4c6bb071c0d919b772db:

  MAINTAINERS: Cover the firmware JSON schema (2020-07-27 10:28:28 -0400)

----------------------------------------------------------------
virtio,pci: bugfixes

Minor bugfixes all over the places, including one CVE.

Additionally, a fix for an ancient bug in migration -
one has to wonder how come no one noticed.

The fix is also non-trivial since we dare not break all
existing machine types with pci - we have a work around
in the works, for now we just skip the work-around for
old machine types.

Great job by Hogan Wang noticing, debugging and fixing it,
and thanks to Dr. David Alan Gilbert for reviewing the patches.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Cindy Lu (1):
      vhost-vdpa :Fix Coverity CID 1430270 / CID 1420267

David Hildenbrand (1):
      virtio-mem-pci: force virtio version 1

Hogan Wang (1):
      hw/pci-host: save/restore pci host config register

Philippe Mathieu-Daudé (2):
      libvhost-user: Report descriptor index on panic
      MAINTAINERS: Cover the firmware JSON schema

Raphael Norwitz (1):
      Fix vhost-user buffer over-read on ram hot-unplug

 include/hw/pci/pci_host.h             |  1 +
 contrib/libvhost-user/libvhost-user.c |  4 ++--
 hw/core/machine.c                     |  1 +
 hw/i386/pc.c                          |  3 ++-
 hw/pci/pci_host.c                     | 33 +++++++++++++++++++++++++++++++++
 hw/virtio/vhost-user.c                |  2 +-
 hw/virtio/vhost-vdpa.c                |  4 ++--
 hw/virtio/virtio-mem-pci.c            |  4 ++--
 MAINTAINERS                           |  8 ++++++++
 9 files changed, 52 insertions(+), 8 deletions(-)



             reply	other threads:[~2020-07-27 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 14:31 Michael S. Tsirkin [this message]
2020-07-27 14:32 ` [PULL v2 1/6] virtio-mem-pci: force virtio version 1 Michael S. Tsirkin
2020-07-27 14:32 ` [PULL v2 2/6] hw/pci-host: save/restore pci host config register Michael S. Tsirkin
2020-07-27 14:32 ` [PULL v2 3/6] Fix vhost-user buffer over-read on ram hot-unplug Michael S. Tsirkin
2020-07-27 14:32 ` [PULL v2 4/6] libvhost-user: Report descriptor index on panic Michael S. Tsirkin
2020-07-27 14:32 ` [PULL v2 5/6] vhost-vdpa :Fix Coverity CID 1430270 / CID 1420267 Michael S. Tsirkin
2020-07-27 14:32 ` [PULL v2 6/6] MAINTAINERS: Cover the firmware JSON schema Michael S. Tsirkin
2020-07-28  8:14 ` [PULL v2 0/6] virtio,pci: bugfixes Peter Maydell

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=20200727143104.97776-1-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).