All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com
Subject: [PULL 0/2] VFIO updates 2022-09-27
Date: Tue, 27 Sep 2022 16:28:46 -0600	[thread overview]
Message-ID: <166431760265.2571033.4930197108505513269.stgit@omen> (raw)

The following changes since commit dbc4f48b5ab3e6d85f78aa4df6bd6ad561c3d152:

  Merge tag 'net-pull-request' of https://github.com/jasowang/qemu into staging (2022-09-27 11:08:36 -0400)

are available in the Git repository at:

  https://gitlab.com/alex.williamson/qemu.git tags/vfio-updates-20220927.1

for you to fetch changes up to 85b6d2b5fc25c9c0d10d493b3728183ab8f8e68a:

  vfio/common: Fix vfio_iommu_type1_info use after free (2022-09-27 14:26:42 -0600)

----------------------------------------------------------------
VFIO updates 2022-09-27

 * Fix initial values for migration state (Kunkun Jiang)

 * Fix a use-after-free error path (Alex Williamson)

----------------------------------------------------------------
Alex Williamson (1):
      vfio/common: Fix vfio_iommu_type1_info use after free

Kunkun Jiang (1):
      vfio/migration: Fix incorrect initialization value for parameters in VFIOMigration

 hw/vfio/common.c    | 36 +++++++++++++++++++-----------------
 hw/vfio/migration.c |  2 ++
 2 files changed, 21 insertions(+), 17 deletions(-)



             reply	other threads:[~2022-09-27 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 22:28 Alex Williamson [this message]
2022-09-27 22:29 ` [PULL 1/2] vfio/migration: Fix incorrect initialization value for parameters in VFIOMigration Alex Williamson
2022-09-27 22:29 ` [PULL 2/2] vfio/common: Fix vfio_iommu_type1_info use after free Alex Williamson

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=166431760265.2571033.4930197108505513269.stgit@omen \
    --to=alex.williamson@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.