From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>
Subject: Re: [RFC 2/2] drivers/iommu: Unroll unsuccessful mapping
Date: Wed, 27 May 2026 16:36:24 +0200 [thread overview]
Message-ID: <aa9ed4e294988640d886fd8990079f318a5aa003.camel@linux.intel.com> (raw)
In-Reply-To: <20260527140804.2866189-3-krzysztof.karas@intel.com>
Hi Krzysztof,
On Wed, 2026-05-27 at 14:08 +0000, Krzysztof Karas wrote:
> Currently, if iommu maps fewer bytes than requested (iova_len),
> it proceeds to free the iova, but never tries to unmap already
> touched bytes. This behavior may cause memory hogging down the
> line.
>
> Correct that by unmapping before exiting.
>
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> ---
> drivers/iommu/dma-iommu.c | 10 ++++++++--
You have to submit this patch to IOMMU DMA-API LAYER maintainers (see
MAINTAINERS file for list and maintainer addresses) in order to get binding
comments, I believe.
Thanks,
Janusz
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> index 54d96e847f16..64ac2bdfc574 100644
> --- a/drivers/iommu/dma-iommu.c
> +++ b/drivers/iommu/dma-iommu.c
> @@ -1515,8 +1515,14 @@ int iommu_dma_map_sg(struct device *dev, struct scatterlist *sg, int nents,
> * implementation - it knows better than we do.
> */
> ret = iommu_map_sg(domain, iova, sg, nents, prot, GFP_ATOMIC);
> - if (ret < 0 || ret < iova_len)
> + if (ret < 0 || ret < iova_len) {
> + if (ret > 0) {
> + /* Unmap partially mapped bytes before freeing IOVA */
> + if (iommu_unmap(domain, iova, ret) != ret)
> + ret = -EIO;
> + }
> goto out_free_iova;
> + }
>
> return __finalise_sg(dev, sg, nents, iova);
>
> @@ -1525,7 +1531,7 @@ int iommu_dma_map_sg(struct device *dev, struct scatterlist *sg, int nents,
> out_restore_sg:
> __invalidate_sg(sg, nents);
> out:
> - if (ret != -ENOMEM && ret != -EREMOTEIO)
> + if (ret != -ENOMEM && ret != -EREMOTEIO && ret != -EIO)
> return -EINVAL;
> return ret;
> }
next prev parent reply other threads:[~2026-05-27 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 14:08 [RFC 0/2] Improve memory management for large object allocations when i915/shmem is used with iommu Krzysztof Karas
2026-05-27 14:08 ` [RFC 1/2] drm/i915/shmem: Prevent overflows on small segments Krzysztof Karas
2026-05-27 14:29 ` Janusz Krzysztofik
2026-05-28 13:55 ` Sebastian Brzezinka
2026-05-29 11:25 ` Janusz Krzysztofik
2026-06-01 6:13 ` Krzysztof Karas
2026-05-27 14:08 ` [RFC 2/2] drivers/iommu: Unroll unsuccessful mapping Krzysztof Karas
2026-05-27 14:36 ` Janusz Krzysztofik [this message]
2026-05-27 15:04 ` ✗ i915.CI.BAT: failure for Improve memory management for large object allocations when i915/shmem is used with iommu Patchwork
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=aa9ed4e294988640d886fd8990079f318a5aa003.camel@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=sebastian.brzezinka@intel.com \
/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