From: Pranjal Shrivastava <praan@google.com>
To: Mostafa Saleh <smostafa@google.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
joro@8bytes.org, robin.murphy@arm.com, will@kernel.org,
jgg@ziepe.ca, baolu.lu@linux.intel.com, kevin.tian@intel.com
Subject: Re: [PATCH] iommu/pages: Fix iommu_pages_flush_incoherent() for non-x86
Date: Sat, 25 Apr 2026 05:36:15 +0000 [thread overview]
Message-ID: <aexSz6tANRfo0D_y@google.com> (raw)
In-Reply-To: <20260424115051.2082174-1-smostafa@google.com>
On Fri, Apr 24, 2026 at 11:50:51AM +0000, Mostafa Saleh wrote:
> The dma_sync_single_for_device() function expects a dma_addr_t, but
> iommu_pages_flush_incoherent() was incorrectly passing a virtual
> address.
>
> Since iommu_pages_start_incoherent() enforces a 1:1 mapping between
> DMA addresses and physical addresses (checked via WARN_ON), we can
> convert the virtual address to a physical address before passing it to
> the DMA API.
>
> This also matches the behaviour of the other non-x86 in
> iommu_pages_free_incoherent(), which uses virt_to_phys(virt);
>
> Fixes: 36ae67b13976 ("iommu/pages: Add support for incoherent IOMMU page table walkers")
> Signed-off-by: Mostafa Saleh <smostafa@google.com>
> ---
> drivers/iommu/iommu-pages.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/iommu-pages.h b/drivers/iommu/iommu-pages.h
> index ae9da4f571f6..e9e605b5fa3a 100644
> --- a/drivers/iommu/iommu-pages.h
> +++ b/drivers/iommu/iommu-pages.h
> @@ -137,7 +137,7 @@ static inline void iommu_pages_flush_incoherent(struct device *dma_dev,
> void *virt, size_t offset,
> size_t len)
> {
> - dma_sync_single_for_device(dma_dev, (uintptr_t)virt + offset, len,
> + dma_sync_single_for_device(dma_dev, virt_to_phys(virt) + offset, len,
> DMA_TO_DEVICE);
> }
> void iommu_pages_stop_incoherent_list(struct iommu_pages_list *list,
Nice catch!
Additionally, I think we should update the comment in
iommu_pages_start_incoherent() to clarify the restriction. The current
comment says:
"The DMA API is not allowed to do anything other than DMA direct."
But dma_direct actually handles bus offsets perfectly fine. However,
this code fails on platforms with a bus offset is because of the strict
check:
WARN_ON(dma != virt_to_phys(virt))
which enforces a strict 1:1 mapping.
So saying that we only allow dma_direct is a bit misleading as to why
bus offsets fail here. We should update that comment to something like:
diff --git a/drivers/iommu/iommu-pages.c b/drivers/iommu/iommu-pages.c
index 3bab175d8557..3904de686206 100644
--- a/drivers/iommu/iommu-pages.c
+++ b/drivers/iommu/iommu-pages.c
@@ -161,9 +161,11 @@ int iommu_pages_start_incoherent(void *virt, struct device *dma_dev)
return -EINVAL;
/*
- * The DMA API is not allowed to do anything other than DMA
- * direct. It would be nice to also check
- * dev_is_dma_coherent(dma_dev));
+ * We enforce a strict 1:1 mapping (dma == phys). This means
+ * platforms with a bus offset or those that require translation for
+ * the IOMMU's own memory are not supported, even though dma_direct
+ * could otherwise handle bus offsets.
+ * It would be nice to also check dev_is_dma_coherent(dma_dev));
*/
if (WARN_ON(dma != virt_to_phys(virt))) {
dma_unmap_single(dma_dev, dma, ioptdesc_mem_size(iopt),
For the fix:
Reviewed-by: Pranjal Shrivastava <praan@google.com>
Thanks,
Praan
next prev parent reply other threads:[~2026-04-25 5:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 11:50 [PATCH] iommu/pages: Fix iommu_pages_flush_incoherent() for non-x86 Mostafa Saleh
2026-04-24 13:07 ` Jason Gunthorpe
2026-04-25 5:36 ` Pranjal Shrivastava [this message]
2026-04-27 2:50 ` Baolu Lu
2026-04-27 11:59 ` Jörg Rödel
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=aexSz6tANRfo0D_y@google.com \
--to=praan@google.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.