| commit | ebe1504e10f771f4fc5d005a6d1ed3f30e3ad428 | |
| author | Zhenzhong Duan <zhenzhong.duan@intel.com> | |
| Thu, 15 Jun 2023 03:26:26 +0000 (15 11:26 +0800) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Mon, 26 Jun 2023 13:50:00 +0000 (26 09:50 -0400) | ||
| tree | d800efcb6edd745a53e1f0bb1a89dda6e5d24277 | treesnapshot (tar.gz zip) |
| parent | ce735ff03349eeac9efe59c118d78f088a151ec4 | commitdiff |
intel_iommu: Fix address space unmap
During address space unmap, corresponding IOVA tree entries are
also removed. But DMAMap is set beyond notifier's scope by 1, so
in theory there is possibility to remove a continuous entry above
the notifier's scope but falling in adjacent notifier's scope.
There is no issue currently as no use cases allocate notifiers
continuously, but let's be robust.
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Message-Id: <20230615032626.314476-4-zhenzhong.duan@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
During address space unmap, corresponding IOVA tree entries are
also removed. But DMAMap is set beyond notifier's scope by 1, so
in theory there is possibility to remove a continuous entry above
the notifier's scope but falling in adjacent notifier's scope.
There is no issue currently as no use cases allocate notifiers
continuously, but let's be robust.
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Message-Id: <20230615032626.314476-4-zhenzhong.duan@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| hw/i386/intel_iommu.c | diffblobblamehistory |