summaryrefslogtreecommitdiffstats
path: root/tools/testing/radix-tree/maple.c
diff options
context:
space:
mode:
authorAshish Mhetre <amhetre@nvidia.com>2023-12-05 07:56:56 +0100
committerJoerg Roedel <jroedel@suse.de>2023-12-19 14:35:54 +0100
commitbb57f6705960bebeb832142ce9abf43220c3eab1 (patch)
treec5b079ec1144b7a0d3817b853e5fea15f65b2127 /tools/testing/radix-tree/maple.c
parentiommu/sva: Fix memory leak in iommu_sva_bind_device() (diff)
downloadlinux-bb57f6705960bebeb832142ce9abf43220c3eab1.tar.xz
linux-bb57f6705960bebeb832142ce9abf43220c3eab1.zip
iommu: Don't reserve 0-length IOVA region
When the bootloader/firmware doesn't setup the framebuffers, their address and size are 0 in "iommu-addresses" property. If IOVA region is reserved with 0 length, then it ends up corrupting the IOVA rbtree with an entry which has pfn_hi < pfn_lo. If we intend to use display driver in kernel without framebuffer then it's causing the display IOMMU mappings to fail as entire valid IOVA space is reserved when address and length are passed as 0. An ideal solution would be firmware removing the "iommu-addresses" property and corresponding "memory-region" if display is not present. But the kernel should be able to handle this by checking for size of IOVA region and skipping the IOVA reservation if size is 0. Also, add a warning if firmware is requesting 0-length IOVA region reservation. Fixes: a5bf3cfce8cb ("iommu: Implement of_iommu_get_resv_regions()") Signed-off-by: Ashish Mhetre <amhetre@nvidia.com> Acked-by: Robin Murphy <robin.murphy@arm.com> Link: https://lore.kernel.org/r/20231205065656.9544-1-amhetre@nvidia.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'tools/testing/radix-tree/maple.c')
0 files changed, 0 insertions, 0 deletions