patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>
Cc: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Joerg Roedel <joerg.roedel@amd.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	patches@lists.linux.dev, Samiullah Khawaja <skhawaja@google.com>
Subject: [PATCH] iommupt: Fix unlikely flows in increase_top()
Date: Thu, 20 Nov 2025 14:47:42 -0400	[thread overview]
Message-ID: <0-v1-93d0836a0e54+aee-iommupt_increase_fix_jgg@nvidia.com> (raw)

Since increase_top() does it's own READ_ONCE() on top_of_table, the
caller's prior READ_ONCE() could be inconsistent and the first time
through the loop we may actually already have the right level if two
threads are racing map.

In this case new_level will be left uninitialized.

Further all the exits from the loop have to either commit to the new top
or free any memory allocated so the early return must be a goto err_free.

Make it so the only break from the loop always sets new_level to the right
value and all other exits go to err_free. Use pts.level (the pts
represents the top we are stacking) within the loop instead of new_level.

Fixes: dcd6a011a8d5 ("iommupt: Add map_pages op")
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Closes: https://lore.kernel.org/r/aRwgNW9PiW2j-Qwo@stanley.mountain
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
 drivers/iommu/generic_pt/iommu_pt.h | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/drivers/iommu/generic_pt/iommu_pt.h b/drivers/iommu/generic_pt/iommu_pt.h
index 0e046fe0eea34c..032d04ec7b568d 100644
--- a/drivers/iommu/generic_pt/iommu_pt.h
+++ b/drivers/iommu/generic_pt/iommu_pt.h
@@ -683,8 +683,11 @@ static int increase_top(struct pt_iommu *iommu_table, struct pt_range *range,
 		top_range.va = range->va;
 		top_range.last_va = range->last_va;
 
-		if (!pt_check_range(&top_range) && map->leaf_level <= pts.level)
+		if (!pt_check_range(&top_range) &&
+		    map->leaf_level <= pts.level) {
+			new_level = pts.level;
 			break;
+		}
 
 		pts.level++;
 		if (pts.level > PT_MAX_TOP_LEVEL ||
@@ -693,17 +696,18 @@ static int increase_top(struct pt_iommu *iommu_table, struct pt_range *range,
 			goto err_free;
 		}
 
-		new_level = pts.level;
 		table_mem =
 			table_alloc_top(common, _pt_top_set(NULL, pts.level),
 					map->attrs.gfp, ALLOC_DEFER_COHERENT_FLUSH);
-		if (IS_ERR(table_mem))
-			return PTR_ERR(table_mem);
+		if (IS_ERR(table_mem)) {
+			ret = PTR_ERR(table_mem);
+			goto err_free;
+		}
 		iommu_pages_list_add(&free_list, table_mem);
 
 		/* The new table links to the lower table always at index 0 */
 		top_range.va = 0;
-		top_range.top_level = new_level;
+		top_range.top_level = pts.level;
 		pts.table_lower = pts.table;
 		pts.table = table_mem;
 		pt_load_single_entry(&pts);
@@ -735,7 +739,8 @@ static int increase_top(struct pt_iommu *iommu_table, struct pt_range *range,
 	 */
 	domain_lock = iommu_table->driver_ops->get_top_lock(iommu_table);
 	spin_lock_irqsave(domain_lock, flags);
-	if (common->top_of_table != top_of_table) {
+	if (common->top_of_table != top_of_table ||
+	    top_of_table == new_top_of_table) {
 		spin_unlock_irqrestore(domain_lock, flags);
 		ret = -EAGAIN;
 		goto err_free;

base-commit: 30dc4423a35507df9378a6eb1a7104f788f4bbb9
-- 
2.43.0


             reply	other threads:[~2025-11-20 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 18:47 Jason Gunthorpe [this message]
2025-11-21  7:22 ` [PATCH] iommupt: Fix unlikely flows in increase_top() Tian, Kevin
2025-11-21  9:41 ` Vasant Hegde

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=0-v1-93d0836a0e54+aee-iommupt_increase_fix_jgg@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alejandro.j.jimenez@oracle.com \
    --cc=dan.carpenter@linaro.org \
    --cc=iommu@lists.linux.dev \
    --cc=joerg.roedel@amd.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=patches@lists.linux.dev \
    --cc=robin.murphy@arm.com \
    --cc=skhawaja@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).