From: Nicolas Saenz Julienne <nsaenz@amazon.com>
To: Eugene Koira <eugkoira@amazon.com>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Cc: <dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
<joro@8bytes.org>, <will@kernel.org>, <robin.murphy@arm.com>,
<longpeng2@huawei.com>, <graf@amazon.de>, <nsaenz@amazon.com>,
<nh-open-source@amazon.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] iommu/intel: Fix __domain_mapping()'s usage of switch_to_super_page()
Date: Tue, 26 Aug 2025 14:55:58 +0000 [thread overview]
Message-ID: <DCCG3711VAN4.9QEOBBP433L2@amazon.com> (raw)
In-Reply-To: <20250826143816.38686-1-eugkoira@amazon.com>
On Tue Aug 26, 2025 at 2:38 PM UTC, Eugene Koira wrote:
> switch_to_super_page() assumes the memory range it's working on is aligned
> to the target large page level. Unfortunately, __domain_mapping() doesn't
> take this into account when using it, and will pass unaligned ranges
> ultimately freeing a PTE range larger than expected.
>
> Take for example a mapping with the following iov_pfn range [0x3fe400,
> 0x4c0600], which should be backed by the following mappings:
>
> iov_pfn [0x3fe400, 0x3fffff] covered by 2MiB pages
> iov_pfn [0x400000, 0x4bffff] covered by 1GiB pages
> iov_pfn [0x4c0000, 0x4c05ff] covered by 2MiB pages
>
> Under this circumstance, __domain_mapping() will pass [0x400000, 0x4c05ff]
> to switch_to_super_page() at a 1 GiB granularity, which will in turn
> free PTEs all the way to iov_pfn 0x4fffff.
>
> Mitigate this by rounding down the iov_pfn range passed to
> switch_to_super_page() in __domain_mapping()
> to the target large page level.
>
> Additionally add range alignment checks to switch_to_super_page.
>
> Fixes: 9906b9352a35 ("iommu/vt-d: Avoid duplicate removing in __domain_mapping()")
> Signed-off-by: Eugene Koira <eugkoira@amazon.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/iommu/intel/iommu.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 9c3ab9d9f69a..dff2d895b8ab 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -1575,6 +1575,10 @@ static void switch_to_super_page(struct dmar_domain *domain,
> unsigned long lvl_pages = lvl_to_nr_pages(level);
> struct dma_pte *pte = NULL;
>
> + if (WARN_ON(!IS_ALIGNED(start_pfn, lvl_pages) ||
> + !IS_ALIGNED(end_pfn + 1, lvl_pages)))
It might make sense to downgrade the warning to WARN_ON_ONCE().
Other than that:
Reviewed-by: Nicolas Saenz Julienne <nsaenz@amazon.com>
Regards,
Nicolas
next prev parent reply other threads:[~2025-08-26 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 14:38 [PATCH] iommu/intel: Fix __domain_mapping()'s usage of switch_to_super_page() Eugene Koira
2025-08-26 14:55 ` Nicolas Saenz Julienne [this message]
2025-08-26 15:48 ` David Woodhouse
2025-08-28 6:33 ` Baolu Lu
2025-08-28 7:29 ` David Woodhouse
2025-09-01 5:55 ` Baolu Lu
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=DCCG3711VAN4.9QEOBBP433L2@amazon.com \
--to=nsaenz@amazon.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eugkoira@amazon.com \
--cc=graf@amazon.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=nh-open-source@amazon.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--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