From: Robin Murphy <robin.murphy@arm.com>
To: Ashish Mhetre <amhetre@nvidia.com>,
joro@8bytes.org, will@kernel.org, robh@kernel.org,
treding@nvidia.com
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] iommu: Don't reserve IOVA when address and size are zero
Date: Thu, 23 Nov 2023 11:13:13 +0000 [thread overview]
Message-ID: <2ba7bab4-daee-4883-acd4-ec9a10c82103@arm.com> (raw)
In-Reply-To: <20231123061201.16614-1-amhetre@nvidia.com>
On 2023-11-23 6:12 am, Ashish Mhetre wrote:
> When the bootloader/firmware doesn't setup the framebuffers, their
> address and size are zero in "iommu-addresses" property. If we intend to
> use display driver in kernel without framebuffer then it's causing
> the display IOMMU mappings to fail as IOVA is reserved with size and
> address as zero.
Can you clarify the problem there? Looking at the code in
iova_reserve_iommu_regions() I'm guessing it's that "region->start +
region->length - 1" underflows so reserve_iova() actually ends up
reserving the entire valid IOVA space?
> 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 and
> address of IOVA and skipping the IOVA reservation if both are 0.
Surely it doesn't make sense to reserve a 0-length region at *any* base
address? The symptom above wouldn't be quite the same if the base was
nonzero, but corrupting the rbtree with an entry where pfn_hi < pfn_lo
would definitely not be good either.
> Fixes: a5bf3cfce8cb ("iommu: Implement of_iommu_get_resv_regions()")
> Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
> ---
> drivers/iommu/of_iommu.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> index 157b286e36bf..150ef65d357a 100644
> --- a/drivers/iommu/of_iommu.c
> +++ b/drivers/iommu/of_iommu.c
> @@ -255,6 +255,10 @@ void of_iommu_get_resv_regions(struct device *dev, struct list_head *list)
> size_t length;
>
> maps = of_translate_dma_region(np, maps, &iova, &length);
> + if (iova == 0 && length == 0) {
> + dev_dbg(dev, "Skipping IOVA reservation as address and size are zero\n");
FWIW I'd be inclined to log a visible warning that firmware is giving us
nonsense.
Thanks,
Robin.
> + continue;
> + }
> type = iommu_resv_region_get_type(dev, &phys, iova, length);
>
> region = iommu_alloc_resv_region(iova, length, prot, type,
next prev parent reply other threads:[~2023-11-23 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 6:12 [PATCH] iommu: Don't reserve IOVA when address and size are zero Ashish Mhetre
2023-11-23 11:13 ` Robin Murphy [this message]
2023-11-28 8:11 ` Ashish Mhetre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ba7bab4-daee-4883-acd4-ec9a10c82103@arm.com \
--to=robin.murphy@arm.com \
--cc=amhetre@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=treding@nvidia.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox