summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorLu Baolu <baolu.lu@linux.intel.com>2025-01-17 08:58:00 +0300
committerJoerg Roedel <jroedel@suse.de>2025-02-10 16:49:30 +0300
commit9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08 (patch)
tree48f551a755df9b44410e18a776605408fc1924a9 /tools/perf/scripts/python
parenta64dcfb451e254085a7daee5fe51bf22959d52d3 (diff)
downloadlinux-9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08.tar.xz
iommu: Fix potential memory leak in iopf_queue_remove_device()
The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf's with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue. However, it fails to release the group structure that represents a group of iopf's awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf's. Fix it by calling iopf_free_group() after the iopf group is responded. Fixes: 199112327135 ("iommu: Track iopf group instead of last fault") Cc: stable@vger.kernel.org Suggested-by: Kevin Tian <kevin.tian@intel.com> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Link: https://lore.kernel.org/r/20250117055800.782462-1-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions