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" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO fix for v6.6-rc4
Date: Tue, 26 Sep 2023 15:45:38 -0600	[thread overview]
Message-ID: <20230926154538.20a5b2c4.alex.williamson@redhat.com> (raw)

Hi Linus,

The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70:

  Linux 6.6-rc2 (2023-09-17 14:40:24 -0700)

are available in the Git repository at:

  https://github.com/awilliam/linux-vfio.git tags/vfio-v6.6-rc4

for you to fetch changes up to c777b11d34e0f47dbbc4b018ef65ad030f2b283a:

  vfio/mdev: Fix a null-ptr-deref bug for mdev_unregister_parent() (2023-09-22 12:48:04 -0600)

----------------------------------------------------------------
VFIO fixes for v6.6-rc4

 - The new PDS vfio-pci variant driver only supports SR-IOV VF devices
   and incorrectly made a direct reference to the physfn field of the
   pci_dev.  Fix this both by making the Kconfig depend on IOV support
   as well as using the correct wrapper for this access. (Shixiong Ou)

 - Resolve an error path issue where on unwind of the mdev registration
   the created kset is not unregistered and the wrong error code is
   returned. (Jinjie Ruan)

----------------------------------------------------------------
Jinjie Ruan (1):
      vfio/mdev: Fix a null-ptr-deref bug for mdev_unregister_parent()

Shixiong Ou (2):
      vfio/pds: Add missing PCI_IOV depends
      vfio/pds: Use proper PF device access helper

 drivers/vfio/mdev/mdev_sysfs.c  | 3 ++-
 drivers/vfio/pci/pds/Kconfig    | 2 +-
 drivers/vfio/pci/pds/vfio_dev.c | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)


             reply	other threads:[~2023-09-26 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 21:45 Alex Williamson [this message]
2023-09-27 17:10 ` 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=20230926154538.20a5b2c4.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®