aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
diff options
context:
space:
mode:
authorJacob Pan <[email protected]>2025-06-18 23:46:18 +0000
committerAlex Williamson <[email protected]>2025-07-11 20:43:38 +0000
commit982ddd59ed97dc7e63efd97ed50273ffb817bd41 (patch)
treedcaa3b7ca4f1f1bba1c4d605690ed662f7cb9594 /drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
parentvfio: Fix unbalanced vfio_df_close call in no-iommu mode (diff)
downloadkernel-982ddd59ed97dc7e63efd97ed50273ffb817bd41.tar.gz
kernel-982ddd59ed97dc7e63efd97ed50273ffb817bd41.zip
vfio: Prevent open_count decrement to negative
When vfio_df_close() is called with open_count=0, it triggers a warning in vfio_assert_device_open() but still decrements open_count to -1. This allows a subsequent open to incorrectly pass the open_count == 0 check, leading to unintended behavior, such as setting df->access_granted = true. For example, running an IOMMUFD compat no-IOMMU device with VFIO tests (https://github.com/awilliam/tests/blob/master/vfio-noiommu-pci-device-open.c) results in a warning and a failed VFIO_GROUP_GET_DEVICE_FD ioctl on the first run, but the second run succeeds incorrectly. Add checks to avoid decrementing open_count below zero. Fixes: 05f37e1c03b6 ("vfio: Pass struct vfio_device_file * to vfio_device_open/close()") Reviewed-by: Jason Gunthorpe <[email protected]> Reviewed-by: Yi Liu <[email protected]> Signed-off-by: Jacob Pan <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alex Williamson <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c')
0 files changed, 0 insertions, 0 deletions