vfio/pci: Check the device set open count on reset
Subsystems (2)
v6 cover vfio/pci: Check the device set open count on reset
This series fixes an issue where devices bound to vfio-pci are not reset when they are released. Skipping the reset has unpredictable results depending on the device, and can cause errors when accessing the device later or binding to a different driver.
The first patch in this series fixes a life cycle issue that was discovered in an earlier revision of the series.
Thank you Alex, Jason, and Kevin for your reviews and feedback. This revision includes the changes suggested on v5, but without any changes to vfio_device_set_open_count().
Anthony
v5 -> v6:
- Added a call to lockdep_assert_held() in patch 3
- Corrected "vfio_container_device_register()" in the patch 1 commit message
v5: https://lore.kernel.org/kvm/[email protected]/
v4 -> v5:
- Replaced patch 2 with a patch that introduces a new function to get the open count of a device set
- Updated patch 3 to use the new function
v4: https://lore.kernel.org/kvm/[email protected]/
v3 -> v4:
- Added a patch to fix device registration life cycle
- Added a patch to add a public open_count on vfio_device_set
- Changed the implementation to avoid private open_count usage
v3: https://lore.kernel.org/kvm/[email protected]/
v2 -> v3:
- Added WARN_ON()
- Revised commit message
v2: https://lore.kernel.org/kvm/[email protected]/
v1 -> v2:
- Changed reset behavior instead of open_count ordering
- Retitled from "vfio: Decrement open_count before close_device()"
v1: https://lore.kernel.org/kvm/[email protected]/
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(-)
Signature · 1 line
2.37.4
PATCH v6 1/3 vfio: Fix container device registration life cycle
In vfio_device_open(), vfio_device_container_register() is always called when open_count == 1. On error, vfio_device_container_unregister() is only called when open_count == 1 and close_device is set. This leaks a registration for devices without a close_device implementation.
In vfio_device_fops_release(), vfio_device_container_unregister() is called unconditionally. This can cause a device to be unregistered multiple times.
Treating container device registration/unregistration uniformly (always when open_count == 1) fixes both issues.
--- drivers/vfio/vfio_main.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
drivers/vfio/vfio_main.c +8 -5
@@ -801,8 +801,9 @@ static struct file *vfio_device_open(struct vfio_device *device) err_close_device:mutex_lock (&device->dev_set->lock);mutex_lock (&device->group->group_lock); -if (device->open_count ==1 && device->ops->close_device) { - device->ops->close_device (device); +if (device->open_count ==1 ) { +if (device->ops->close_device) + device->ops->close_device (device);vfio_device_container_unregister (device); }
@@ -1017,10 +1018,12 @@ static int vfio_device_fops_release(struct inode *inode, struct file *filep)mutex_lock (&device->dev_set->lock);vfio_assert_device_open (device);mutex_lock (&device->group->group_lock); -if (device->open_count ==1 && device->ops->close_device) - device->ops->close_device (device); +if (device->open_count ==1 ) { +if (device->ops->close_device) + device->ops->close_device (device); -vfio_device_container_unregister (device); +vfio_device_container_unregister (device); + }mutex_unlock (&device->group->group_lock); device->open_count--;if (device->open_count ==0 )
Signature · 1 line
2.37.4
Re: [PATCH v6 1/3] vfio: Fix container device registration life cycle
Quoted 12 lines · Anthony DeRossi
In
vfio_device_open(),vfio_device_container_register()is always called whenopen_count== 1. On error,vfio_device_container_unregister()is only called whenopen_count== 1 andclose_deviceis set. This leaks a registration for devices without aclose_deviceimplementation.In
vfio_device_fops_release(),vfio_device_container_unregister()is called unconditionally. This can cause a device to be unregistered multiple times.Treating container device registration/unregistration uniformly (always when
open_count== 1) fixes both issues.
Quoted 7 lines
Fixes ce4b4657ff18 ("vfio: Replace the DMA unmapping notifier with a callback")Signed-off-by Anthony DeRossi <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Reviewed-by Kevin Tian <[email protected]>--- drivers/vfio/vfio_main.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
Quoted 32 lines
drivers/vfio/vfio_main.c +8
-5@@ -801,8 +801,9 @@ static struct file *vfio_device_open(struct vfio_device *device) err_close_device:mutex_lock (&device->dev_set->lock);mutex_lock (&device->group->group_lock); -if (device->open_count ==1 && device->ops->close_device) { - device->ops->close_device (device); +if (device->open_count ==1 ) { +if (device->ops->close_device) + device->ops->close_device (device);vfio_device_container_unregister (device); }@@ -1017,10 +1018,12 @@ static int vfio_device_fops_release(struct inode *inode, struct file *filep)mutex_lock (&device->dev_set->lock);vfio_assert_device_open (device);mutex_lock (&device->group->group_lock); -if (device->open_count ==1 && device->ops->close_device) - device->ops->close_device (device); +if (device->open_count ==1 ) { +if (device->ops->close_device) + device->ops->close_device (device); -vfio_device_container_unregister (device); +vfio_device_container_unregister (device); + }mutex_unlock (&device->group->group_lock); device->open_count--;if (device->open_count ==0 )
Signature · 2 lines
Regards, Yi Liu
PATCH v6 2/3 vfio: Export the device set open count
In reply to Anthony DeRossiThe open count of a device set is the sum of the open counts of all devices in the set. Drivers can use this value to determine whether shared resources are in use without tracking them manually or accessing the private open_count in vfio_device.
--- drivers/vfio/vfio_main.c | 13 +++++++++++++ include/linux/vfio.h | 1 + 2 files changed, 14 insertions(+)
drivers/vfio/vfio_main.c +13 -0
@@ -125,6 +125,19 @@ static void vfio_release_device_set(struct vfio_device *device)xa_unlock (&vfio_device_set_xa); } +unsigned int vfio_device_set_open_count (struct vfio_device_set *dev_set) +{ +struct vfio_device *cur; +unsigned int open_count =0 ; + +lockdep_assert_held (&dev_set->lock); + +list_for_each_entry (cur, &dev_set->device_list, dev_set_list) + open_count += cur->open_count; +return open_count; +} +EXPORT_SYMBOL_GPL (vfio_device_set_open_count); +/* * Group objects - create, release, get, put, search */
include/linux/vfio.h +1 -0
@@ -189,6 +189,7 @@ int vfio_register_emulated_iommu_dev(struct vfio_device *device);void vfio_unregister_group_dev (struct vfio_device *device);int vfio_assign_device_set (struct vfio_device *device,void *set_id); +unsigned int vfio_device_set_open_count (struct vfio_device_set *dev_set); int vfio_mig_get_next_state(struct vfio_device *device, enum vfio_device_mig_state cur_fsm,
Signature · 1 line
2.37.4
Re: [PATCH v6 2/3] vfio: Export the device set open count
Quoted 5 lines · Anthony DeRossi
The open count of a device set is the sum of the open counts of all devices in the set. Drivers can use this value to determine whether shared resources are in use without tracking them manually or accessing the private
open_countinvfio_device.
Quoted 7 lines
Signed-off-by Anthony DeRossi <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Reviewed-by Kevin Tian <[email protected]>--- drivers/vfio/vfio_main.c | 13 +++++++++++++ include/linux/vfio.h | 1 + 2 files changed, 14 insertions(+)
Quoted 36 lines
drivers/vfio/vfio_main.c +13
-0@@ -125,6 +125,19 @@ static void vfio_release_device_set(struct vfio_device *device)xa_unlock (&vfio_device_set_xa); } +unsigned int vfio_device_set_open_count (struct vfio_device_set *dev_set) +{ +struct vfio_device *cur; +unsigned int open_count =0 ; + +lockdep_assert_held (&dev_set->lock); + +list_for_each_entry (cur, &dev_set->device_list, dev_set_list) + open_count += cur->open_count; +return open_count; +} +EXPORT_SYMBOL_GPL (vfio_device_set_open_count); +/* * Group objects - create, release, get, put, search */ include/linux/vfio.h +1
-0@@ -189,6 +189,7 @@ int vfio_register_emulated_iommu_dev(struct vfio_device *device);void vfio_unregister_group_dev (struct vfio_device *device);int vfio_assign_device_set (struct vfio_device *device,void *set_id); +unsigned int vfio_device_set_open_count (struct vfio_device_set *dev_set); int vfio_mig_get_next_state(struct vfio_device *device, enum vfio_device_mig_state cur_fsm,
Signature · 2 lines
Regards, Yi Liu
PATCH v6 3/3 vfio/pci: Check the device set open count on reset
In reply to Anthony DeRossivfio_pci_dev_set_needs_reset() inspects the open_count of every device in the set to determine whether a reset is allowed. The current device always has open_count == 1 within vfio_pci_core_disable(), effectively disabling the reset logic. This field is also documented as private in vfio_device, so it should not be used to determine whether other devices in the set are open.
Checking for vfio_device_set_open_count() > 1 on the device set fixes both issues.
After commit 2cd8b14aaa66 ("vfio/pci: Move to the device set infrastructure"), failure to create a new file for a device would cause the reset to be skipped due to open_count being decremented after calling close_device() in the error path.
After commit eadd86f835c6 ("vfio: Remove calls to vfio_group_add_container_user()"), releasing a device would always skip the reset due to an ordering change in vfio_device_fops_release().
Failing to reset the device leaves it in an unknown state, potentially causing errors when it is accessed later or bound to a different driver.
This issue was observed with a Radeon RX Vega 56 [1002:687f] (rev c3) assigned to a Windows guest. After shutting down the guest, unbinding the device from vfio-pci, and binding the device to amdgpu:
[ 548.007102] [drm:psp_hw_start [amdgpu]] *ERROR* PSP create ring failed! [ 548.027174] [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed [ 548.027242] [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 [ 548.027306] amdgpu 0000:0a:00.0: amdgpu: amdgpu_device_ip_init failed [ 548.027308] amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init
--- drivers/vfio/pci/vfio_pci_core.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/vfio/pci/vfio_pci_core.c +5 -5
@@ -2488,12 +2488,12 @@ static bool vfio_pci_dev_set_needs_reset(struct vfio_device_set *dev_set)struct vfio_pci_core_device *cur;bool needs_reset = false; -list_for_each_entry (cur, &dev_set->device_list, vdev.dev_set_list) { -/* No VFIO device in the set can have an open device FD */ -if (cur->vdev.open_count) -return false; +/* No other VFIO device in the set can be open. */ +if (vfio_device_set_open_count (dev_set) >1 ) +return false; + +list_for_each_entry (cur, &dev_set->device_list, vdev.dev_set_list) needs_reset |= cur->needs_reset; - }return needs_reset; }
Signature · 1 line
2.37.4
Hi DeRossi,
Quoted 6 lines · Anthony DeRossi
vfio_pci_dev_set_needs_reset()inspects theopen_countof every device in the set to determine whether a reset is allowed. The current device always hasopen_count== 1 withinvfio_pci_core_disable(), effectively disabling the reset logic. This field is also documented as private invfio_device, so it should not be used to determine whether other devices in the set are open.
haven't went through the prior version. maybe may question has been already answered. My question is:
the major reason is the order problem in vfio_main.c. close_device() is always called before decreasing open_count to be 0. So even other device has no open fd, the current vfio_device still have one open count. So why can't we just switch the order of open_count-- and close_device()?
Quoted 2 lines
Checking for
vfio_device_set_open_count()> 1 on the device set fixes both issues
tbh. it's weird to me that a driver needs to know the internal logic of vfio core before knowing it needs to check the vfio_device_set_open_count() in this way. Is vfio-pci the only driver that needs to do this check or there are other drivers? If there are other drivers, maybe fixing the order in core is better.
Quoted 53 lines
After commit
2cd8b14aaa66("vfio/pci: Move to the device set infrastructure"), failure to create a new file for a device would cause the reset to be skipped due toopen_countbeing decremented after callingclose_device()in the error path.After commit
eadd86f835c6("vfio: Remove calls tovfio_group_add_container_user()"), releasing a device would always skip the reset due to an ordering change invfio_device_fops_release().Failing to reset the device leaves it in an unknown state, potentially causing errors when it is accessed later or bound to a different driver.
This issue was observed with a Radeon RX Vega 56 [1002:687f] (rev c3) assigned to a Windows guest. After shutting down the guest, unbinding the device from vfio-pci, and binding the device to amdgpu:
[ 548.007102] [drm:psp_hw_start [amdgpu]] *ERROR* PSP create ring failed! [ 548.027174] [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed [ 548.027242] [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 [ 548.027306] amdgpu 0000:0a:00.0: amdgpu: amdgpu_device_ip_init failed [ 548.027308] amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU initFixes 2cd8b14aaa66 ("vfio/pci: Move to the device set infrastructure")Fixes eadd86f835c6 ("vfio: Remove calls to vfio_group_add_container_user()")Signed-off-by Anthony DeRossi <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Reviewed-by Kevin Tian <[email protected]>--- drivers/vfio/pci/vfio_pci_core.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/vfio/pci/vfio_pci_core.c +5
-5@@ -2488,12 +2488,12 @@ static bool vfio_pci_dev_set_needs_reset(struct vfio_device_set *dev_set)struct vfio_pci_core_device *cur;bool needs_reset = false; -list_for_each_entry (cur, &dev_set->device_list, vdev.dev_set_list) { -/* No VFIO device in the set can have an open device FD */ -if (cur->vdev.open_count) -return false; +/* No other VFIO device in the set can be open. */ +if (vfio_device_set_open_count (dev_set) >1 ) +return false; + +list_for_each_entry (cur, &dev_set->device_list, vdev.dev_set_list) needs_reset |= cur->needs_reset; - }return needs_reset; }
Signature · 2 lines
Regards, Yi Liu
Quoted 10 lines · On Thu, 10 Nov 2022 11:03:29 +0800 Yi Liu <[email protected]> wrote:
Hi DeRossi,
Quoted 6 lines · Anthony DeRossi
vfio_pci_dev_set_needs_reset()inspects theopen_countof every device in the set to determine whether a reset is allowed. The current device always hasopen_count== 1 withinvfio_pci_core_disable(), effectively disabling the reset logic. This field is also documented as private invfio_device, so it should not be used to determine whether other devices in the set are open.
Quoted 7 lines
haven't went through the prior version. maybe may question has been already answered. My question is:
the major reason is the order problem in
vfio_main.c.close_device()is always called before decreasingopen_countto be 0. So even other device has no open fd, the currentvfio_devicestill have one open count. So why can't we just switch the order of open_count-- andclose_device()?
This is what was originally proposed and Jason shot it down:
https://lore.kernel.org/all/[email protected]/
Quoted 7 lines
Quoted 2 lines
Checking for
vfio_device_set_open_count()> 1 on the device set fixes both issuestbh. it's weird to me that a driver needs to know the internal logic of vfio core before knowing it needs to check the
vfio_device_set_open_count()in this way. Is vfio-pci the only driver that needs to do this check or there are other drivers? If there are other drivers, maybe fixing the order in core is better.
Please see the evolution of reflck into device sets. Both PCI and FSL can have multiple devices in a set, AIUI. The driver defines the set. This ability to test for the last close among devices in the set is a fundamental feature of the original reflck. Thanks,
Alex
Quoted 16 lines · Alex Williamson
Quoted 13 lines · On Thu, 10 Nov 2022 11:03:29 +0800 Yi Liu <[email protected]> wrote:
Hi DeRossi,
Quoted 6 lines · Anthony DeRossi
vfio_pci_dev_set_needs_reset()inspects theopen_countof every device in the set to determine whether a reset is allowed. The current device always hasopen_count== 1 withinvfio_pci_core_disable(), effectively disabling the reset logic. This field is also documented as private invfio_device, so it should not be used to determine whether other devices in the set are open.haven't went through the prior version. maybe may question has been already answered. My question is:
Quoted 8 lines
Quoted 4 lines
the major reason is the order problem in
vfio_main.c.close_device()is always called before decreasingopen_countto be 0. So even other device has no open fd, the currentvfio_devicestill have one open count. So why can't we just switch the order of open_count-- andclose_device()?This is what was originally proposed and Jason shot it down:
got it. :-)
Quoted 8 lines
Quoted 7 lines
Quoted 2 lines
Checking for
vfio_device_set_open_count()> 1 on the device set fixes both issuestbh. it's weird to me that a driver needs to know the internal logic of vfio core before knowing it needs to check the
vfio_device_set_open_count()in this way. Is vfio-pci the only driver that needs to do this check or there are other drivers? If there are other drivers, maybe fixing the order in core is better.
Quoted 4 lines
Please see the evolution of reflck into device sets. Both PCI and FSL can have multiple devices in a set, AIUI. The driver defines the set. This ability to test for the last close among devices in the set is a fundamental feature of the original reflck. Thanks,
thanks for the info.
Signature · 2 lines
Regards, Yi Liu
Alex Williamson
AppliedQuoted 46 lines · On Wed, 9 Nov 2022 17:40:24 -0800 Anthony DeRossi <[email protected]> wrote:
This series fixes an issue where devices bound to vfio-pci are not reset when they are released. Skipping the reset has unpredictable results depending on the device, and can cause errors when accessing the device later or binding to a different driver.
The first patch in this series fixes a life cycle issue that was discovered in an earlier revision of the series.
Thank you Alex, Jason, and Kevin for your reviews and feedback. This revision includes the changes suggested on v5, but without any changes to
vfio_device_set_open_count().Anthony
v5 -> v6:
- Added a call tolockdep_assert_held()in patch 3
- Corrected "vfio_container_device_register()" in the patch 1 commit message
v5: https://lore.kernel.org/kvm/[email protected]/v4 -> v5:
- Replaced patch 2 with a patch that introduces a new function to get the open count of a device set
- Updated patch 3 to use the new function
v4: https://lore.kernel.org/kvm/[email protected]/v3 -> v4:
- Added a patch to fix device registration life cycle
- Added a patch to add a publicopen_countonvfio_device_set
- Changed the implementation to avoid privateopen_countusage
v3: https://lore.kernel.org/kvm/[email protected]/v2 -> v3:
- AddedWARN_ON()
- Revised commit message
v2: https://lore.kernel.org/kvm/[email protected]/v1 -> v2:
- Changed reset behavior instead ofopen_countordering
- Retitled from "vfio: Decrementopen_countbeforeclose_device()"
v1: https://lore.kernel.org/kvm/[email protected]/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
Quoted 5 lines
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(-)
Applied to vfio for-linus branch for v6.1. Thanks,
Alex