All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	ajderossi@gmail.com
Subject: [GIT PULL] VFIO fixes for v6.1-rc6
Date: Mon, 14 Nov 2022 12:42:17 -0700	[thread overview]
Message-ID: <20221114124217.784a2d3f.alex.williamson@redhat.com> (raw)

The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:

  Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)

are available in the Git repository at:

  https://github.com/awilliam/linux-vfio.git tags/vfio-v6.1-rc6

for you to fetch changes up to e806e223621e4f5105170df69d7311dc3fb4bbb4:

  vfio/pci: Check the device set open count on reset (2022-11-10 12:03:36 -0700)

----------------------------------------------------------------
VFIO fixes for v6.1-rc6

 - Fixes for potential container registration leak for drivers not
   implementing a close callback, duplicate container de-registrations,
   and a regression in support for bus reset on last device close from
   a device set. (Anthony DeRossi)

----------------------------------------------------------------
Anthony DeRossi (3):
      vfio: Fix container device registration life cycle
      vfio: Export the device set open count
      vfio/pci: Check the device set open count on reset

 drivers/vfio/pci/vfio_pci_core.c | 10 +++++-----
 drivers/vfio/vfio_main.c         | 26 +++++++++++++++++++++-----
 include/linux/vfio.h             |  1 +
 3 files changed, 27 insertions(+), 10 deletions(-)


             reply	other threads:[~2022-11-14 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 19:42 Alex Williamson [this message]
2022-11-14 20:46 ` [GIT PULL] VFIO fixes for v6.1-rc6 pr-tracker-bot

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=20221114124217.784a2d3f.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=ajderossi@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.