mirror of https://lore.kernel.org/lkml/
 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>
Subject: [GIT PULL] VFIO fixes for v6.2-rc6
Date: Mon, 23 Jan 2023 11:20:53 -0700	[thread overview]
Message-ID: <20230123112053.173232a7.alex.williamson@redhat.com> (raw)

Hi Linus,

The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:

  Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)

are available in the Git repository at:

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

for you to fetch changes up to 51cdc8bc120ef6e42f6fb758341f5d91bc955952:

  kvm/vfio: Fix potential deadlock on vfio group_lock (2023-01-20 08:50:05 -0700)

----------------------------------------------------------------
VFIO fixes for v6.2-rc6

 - Honor reserved regions when testing for IOMMU find grained super
   page support, avoiding a regression on s390 for a firmware device
   where the existence of the mapping, even if unused can trigger
   an error state. (Niklas Schnelle)

 - Fix a deadlock in releasing KVM references by using the alternate
   .release() rather than .destroy() callback for the kvm-vfio device.
   (Yi Liu)

----------------------------------------------------------------
Niklas Schnelle (1):
      vfio/type1: Respect IOMMU reserved regions in vfio_test_domain_fgsp()

Yi Liu (1):
      kvm/vfio: Fix potential deadlock on vfio group_lock

 drivers/vfio/vfio_iommu_type1.c | 31 ++++++++++++++++++++-----------
 virt/kvm/vfio.c                 |  6 +++---
 2 files changed, 23 insertions(+), 14 deletions(-)


             reply	other threads:[~2023-01-23 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 18:20 Alex Williamson [this message]
2023-01-23 19:58 ` 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=20230123112053.173232a7.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®