From: Pranjal Shrivastava <praan@google.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: Mostafa Saleh <smostafa@google.com>,
linux-mm@kvack.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, akpm@linux-foundation.org, vbabka@suse.cz,
surenb@google.com, mhocko@suse.com, jackmanb@google.com,
hannes@cmpxchg.org, ziy@nvidia.com, david@redhat.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
rppt@kernel.org, xiaqinxin@huawei.com, rdunlap@infradead.org
Subject: Re: [PATCH v5 3/4] iommu: debug-pagealloc: Track IOMMU pages
Date: Fri, 9 Jan 2026 07:34:33 +0000 [thread overview]
Message-ID: <aWCviSCK7IBddLTn@google.com> (raw)
In-Reply-To: <d6236413-7385-45c5-94ad-8b0f2007f1ac@linux.intel.com>
On Fri, Jan 09, 2026 at 11:28:32AM +0800, Baolu Lu wrote:
> On 1/8/26 19:33, Mostafa Saleh wrote:
> > I have this, it should have the same effect + a WARN, I will include
> > it in the new version
> >
> > diff --git a/drivers/iommu/iommu-debug-pagealloc.c
> > b/drivers/iommu/iommu-debug-pagealloc.c
> > index 5353417e64f9..64ec0795fe4c 100644
> > --- a/drivers/iommu/iommu-debug-pagealloc.c
> > +++ b/drivers/iommu/iommu-debug-pagealloc.c
> > @@ -146,16 +146,12 @@ void __iommu_debug_unmap_end(struct iommu_domain *domain,
> > if (unmapped == size)
> > return;
> >
> > - /*
> > - * If unmap failed, re-increment the refcount, but if it unmapped
> > - * larger size, decrement the extra part.
> > - */
> > + /* If unmap failed, re-increment the refcount. */
> > if (unmapped < size)
> > __iommu_debug_update_iova(domain, iova + unmapped,
> > size - unmapped, true);
> > else
> > - __iommu_debug_update_iova(domain, iova + size,
> > - unmapped - size, false);
> > + WARN_ONCE(1, "iommu: unmap larger than requested is
> > not supported in debug_pagealloc\n");
> > }
> >
> > void iommu_debug_init(void)
>
> How aobut
>
> if ((unmapped == size) || WARN_ON_ONCE(unmapped > size))
> return;
>
> /* If unmap failed, re-increment the refcount. */
> __iommu_debug_update_iova(domain, iova + unmapped, size - unmapped, true);
>
> ?
>
That's nice, We could also print the message as Mostafa mentioned, like:
if ((unmapped == size) || WARN_ON_ONCE(unmapped > size,
"iommu: unmap larger than requested is not supported in
debug_pagealloc\n"))
An explicit "This is unsupported" warning makes it clear IMHO.
If a driver triggers this, at least we know the sanitizer state isn't
supported.
Thanks,
Praan
next prev parent reply other threads:[~2026-01-09 7:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 16:21 [PATCH v5 0/4] iommu: Add IOMMU_DEBUG_PAGEALLOC sanitizer Mostafa Saleh
2026-01-06 16:21 ` [PATCH v5 1/4] iommu: Add page_ext for IOMMU_DEBUG_PAGEALLOC Mostafa Saleh
2026-01-06 18:50 ` David Hildenbrand (Red Hat)
2026-01-07 15:26 ` Pranjal Shrivastava
2026-01-07 16:53 ` David Hildenbrand (Red Hat)
2026-01-08 10:42 ` Mostafa Saleh
2026-01-08 11:53 ` David Hildenbrand (Red Hat)
2026-01-06 16:21 ` [PATCH v5 2/4] iommu: Add calls " Mostafa Saleh
2026-01-06 21:17 ` Samiullah Khawaja
2026-01-07 5:48 ` Baolu Lu
2026-01-07 15:28 ` Pranjal Shrivastava
2026-01-06 16:21 ` [PATCH v5 3/4] iommu: debug-pagealloc: Track IOMMU pages Mostafa Saleh
2026-01-06 21:18 ` Samiullah Khawaja
2026-01-07 15:21 ` Pranjal Shrivastava
2026-01-08 11:06 ` Mostafa Saleh
2026-01-08 11:33 ` Mostafa Saleh
2026-01-09 3:28 ` Baolu Lu
2026-01-09 7:34 ` Pranjal Shrivastava [this message]
2026-01-09 10:58 ` Mostafa Saleh
2026-01-09 11:02 ` Mostafa Saleh
2026-01-06 16:22 ` [PATCH v5 4/4] iommu: debug-pagealloc: Check mapped/unmapped kernel memory Mostafa Saleh
2026-01-06 21:19 ` Samiullah Khawaja
2026-01-07 15:24 ` [PATCH v5 0/4] iommu: Add IOMMU_DEBUG_PAGEALLOC sanitizer Pranjal Shrivastava
2026-01-08 11:37 ` Mostafa Saleh
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=aWCviSCK7IBddLTn@google.com \
--to=praan@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=iommu@lists.linux.dev \
--cc=jackmanb@google.com \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=smostafa@google.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=xiaqinxin@huawei.com \
--cc=ziy@nvidia.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