[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bca59694-6b09-4839-8577-c8ac4420eb56@kernel.org>
Date: Mon, 19 Jan 2026 15:26:57 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Mostafa Saleh <smostafa@...gle.com>, linux-mm@...ck.org,
iommu@...ts.linux.dev, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Cc: corbet@....net, joro@...tes.org, will@...nel.org, robin.murphy@....com,
akpm@...ux-foundation.org, vbabka@...e.cz, surenb@...gle.com,
mhocko@...e.com, jackmanb@...gle.com, hannes@...xchg.org, ziy@...dia.com,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, rppt@...nel.org,
xiaqinxin@...wei.com, baolu.lu@...ux.intel.com, rdunlap@...radead.org
Subject: Re: [PATCH 0/2] iommu: debug-pagealloc: Remove pfn_valid() usage
On 1/19/26 15:22, Mostafa Saleh wrote:
> This is a small fix for the new config IOMMU_DEBUG_PAGEALLOC based
> on the discussion:
> https://lore.kernel.org/linux-iommu/CAFgf54pBAUm3ao-UJksiuGKtvv4wzRyFq_uKwLe0H1ettO4DLQ@mail.gmail.com/
>
> Where it was concluded that pfn_valid() is not enough to validate
> physical addresses before access to page_ext.
>
> The first patch introduces a new function in page_ext that takes a
> physical address as an argument, and the second patch uses it instead
> of calling pfn_valid() and phys_to_page()
>
> Benchmarks with the new implementation can be found in:
> https://lore.kernel.org/linux-iommu/20260114164322.787125-1-smostafa@google.com/
>
> This series applies to iommu/core tree.
This is part of v7 [1], right? Can't we just apply v7 instead or are the
commit IDs already stable?
[1] https://lkml.kernel.org/r/20260114164322.787125-1-smostafa@google.com
--
Cheers
David
Powered by blists - more mailing lists