From: Pranjal Shrivastava <praan@google.com>
To: Alex Williamson <alex@shazbot.org>,
Kevin Tian <kevin.tian@intel.com>,
kvm@vger.kernel.org
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Ankit Agrawal <ankita@nvidia.com>,
Matt Evans <mattev@meta.com>, Leon Romanovsky <leon@kernel.org>,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
Jacob Moroni <jmoroni@google.com>,
David Hu <xuehaohu@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
linux-kernel@vger.kernel.org,
Pranjal Shrivastava <praan@google.com>
Subject: [RFC PATCH v1 1/1] vfio/pci: Revoke BARs and DMABUFs during sysfs-triggered PCI reset
Date: Fri, 7 Aug 2026 20:14:05 +0000 [thread overview]
Message-ID: <20260807201405.3717430-2-praan@google.com> (raw)
In-Reply-To: <20260807201405.3717430-1-praan@google.com>
Currently, vfio-pci does not implement the .reset_prepare and .reset_done
ops in its struct pci_error_handlers. During a sysfs-triggered PCI reset
(echo 1 > /sys/bus/pci/.../reset), the PCI core resets the device using
Function Level Reset (FLR) or Secondary Bus Reset (SBR), which isn't
propagated to the vfio-pci driver. Due to this, the exported DMABUFs and
BARs aren't zapped or revoked and the importer continues to use them.
Implement reset_prepare and reset_done hooks for the vfio-pci driver
that zap the BARs and revoke the exported DMABUFs while holding the
memory_lock.
Signed-off-by: Pranjal Shrivastava <praan@google.com>
---
drivers/vfio/pci/vfio_pci_core.c | 88 ++++++++++++++++++++------------
1 file changed, 56 insertions(+), 32 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
index a113c55845e1..e46b0b1d8a59 100644
--- a/drivers/vfio/pci/vfio_pci_core.c
+++ b/drivers/vfio/pci/vfio_pci_core.c
@@ -1334,12 +1334,14 @@ static int vfio_pci_ioctl_reset(struct vfio_pci_core_device *vdev,
*/
vfio_pci_set_power_state(vdev, PCI_D0);
- vfio_pci_dma_buf_move(vdev, true);
- ret = pci_try_reset_function(vdev->pdev);
- if (__vfio_pci_memory_enabled(vdev))
- vfio_pci_dma_buf_move(vdev, false);
+ /*
+ * Drop the lock before entering the PCI core.
+ * The PCI core will re-acquire it via our .reset_prepare hook.
+ */
up_write(&vdev->memory_lock);
+ ret = pci_try_reset_function(vdev->pdev);
+
return ret;
}
@@ -2418,8 +2420,33 @@ int vfio_pci_core_sriov_configure(struct vfio_pci_core_device *vdev,
}
EXPORT_SYMBOL_GPL(vfio_pci_core_sriov_configure);
+static void vfio_pci_core_reset_prepare(struct pci_dev *pdev)
+{
+ struct vfio_pci_core_device *vdev = dev_get_drvdata(&pdev->dev);
+
+ if (vdev) {
+ down_write(&vdev->memory_lock);
+ vfio_pci_set_power_state(vdev, PCI_D0);
+ vfio_pci_zap_bars(vdev);
+ vfio_pci_dma_buf_move(vdev, true);
+ }
+}
+
+static void vfio_pci_core_reset_done(struct pci_dev *pdev)
+{
+ struct vfio_pci_core_device *vdev = dev_get_drvdata(&pdev->dev);
+
+ if (vdev) {
+ if (__vfio_pci_memory_enabled(vdev))
+ vfio_pci_dma_buf_move(vdev, false);
+ up_write(&vdev->memory_lock);
+ }
+}
+
const struct pci_error_handlers vfio_pci_core_err_handlers = {
.error_detected = vfio_pci_core_aer_err_detected,
+ .reset_prepare = vfio_pci_core_reset_prepare,
+ .reset_done = vfio_pci_core_reset_done,
};
EXPORT_SYMBOL_GPL(vfio_pci_core_err_handlers);
@@ -2561,55 +2588,52 @@ static int vfio_pci_dev_set_hot_reset(struct vfio_device_set *dev_set,
if (!owned) {
ret = -EINVAL;
- break;
+ goto err_out;
}
+ }
+ /* Zap, and set power state */
+ list_for_each_entry(vdev, &dev_set->device_list, vdev.dev_set_list) {
/*
- * Take the memory write lock for each device and zap BAR
- * mappings to prevent the user accessing the device while in
- * reset. Locking multiple devices is prone to deadlock,
+ * Take the memory write lock for each device, zap BAR
+ * mappings, and restore power state before reset.
+ * Locking multiple devices is prone to deadlock,
* runaway and unwind if we hit contention.
*/
if (!down_write_trylock(&vdev->memory_lock)) {
ret = -EBUSY;
- break;
+
+ /*
+ * We failed to lock THIS device. We must step back one
+ * device so err_undo only unlocks devices that succeeded.
+ */
+ if (!list_entry_is_head(vdev, &dev_set->device_list, vdev.dev_set_list)) {
+ vdev = list_prev_entry(vdev, vdev.dev_set_list);
+ goto err_undo;
+ }
+ goto err_out;
}
- vfio_pci_dma_buf_move(vdev, true);
vfio_pci_zap_bars(vdev);
+ vfio_pci_set_power_state(vdev, PCI_D0);
}
- if (!list_entry_is_head(vdev,
- &dev_set->device_list, vdev.dev_set_list)) {
- vdev = list_prev_entry(vdev, vdev.dev_set_list);
- goto err_undo;
- }
-
- /*
- * The pci_reset_bus() will reset all the devices in the bus.
- * The power state can be non-D0 for some of the devices in the bus.
- * For these devices, the pci_reset_bus() will internally set
- * the power state to D0 without vfio driver involvement.
- * For the devices which have NoSoftRst-, the reset function can
- * cause the PCI config space reset without restoring the original
- * state (saved locally in 'vdev->pm_save').
- */
+ /* Drop locks before crossing into PCI core */
list_for_each_entry(vdev, &dev_set->device_list, vdev.dev_set_list)
- vfio_pci_set_power_state(vdev, PCI_D0);
+ up_write(&vdev->memory_lock);
+ /* PCI core handles the reset and calls .reset hooks */
ret = pci_reset_bus(pdev);
- vdev = list_last_entry(&dev_set->device_list,
- struct vfio_pci_core_device, vdev.dev_set_list);
+ goto err_out;
err_undo:
+ /* Unwind locks cleanly for devices we successfully locked */
list_for_each_entry_from_reverse(vdev, &dev_set->device_list,
- vdev.dev_set_list) {
- if (vdev->vdev.open_count && __vfio_pci_memory_enabled(vdev))
- vfio_pci_dma_buf_move(vdev, false);
+ vdev.dev_set_list)
up_write(&vdev->memory_lock);
- }
+err_out:
list_for_each_entry(vdev, &dev_set->device_list, vdev.dev_set_list)
pm_runtime_put(&vdev->pdev->dev);
--
2.55.0.679.g6767b8d81c-goog
next prev parent reply other threads:[~2026-08-07 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 20:14 [RFC PATCH v1 0/1] vfio/pci: Revoke BARs and DMABUFs during sysfs-triggered PCI reset Pranjal Shrivastava
2026-08-07 20:14 ` Pranjal Shrivastava [this message]
2026-08-07 20:30 ` [RFC PATCH v1 1/1] " sashiko-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=20260807201405.3717430-2-praan@google.com \
--to=praan@google.com \
--cc=alex@shazbot.org \
--cc=ankita@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jmoroni@google.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattev@meta.com \
--cc=skhawaja@google.com \
--cc=vivek.kasireddy@intel.com \
--cc=xuehaohu@google.com \
/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