From: Vasant Hegde <vasant.hegde@amd.com>
To: <iommu@lists.linux.dev>, <joro@8bytes.org>
Cc: <suravee.suthikulpanit@amd.com>, <baolu.lu@linux.intel.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: [PATCH v2 iommu/next] iommu: Fix default domain setup
Date: Mon, 19 Jun 2023 08:49:45 +0000 [thread overview]
Message-ID: <20230619084945.6427-1-vasant.hegde@amd.com> (raw)
Commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
accidently restored "group->domain" to "old_domain" while keeping
"group->default_domain" to new domain. Also freed new domain.
This works fine during boot as 'old_domain' is NULL. But if we try
change domain via sysfs using below command then kernel crashes with
"kernel NULL pointer dereference".
Change domain command :
- Go to /sys/kernel/iommu_groups/<group id>/
- Unbind device driver for all devices in the group
- echo "<dom type>" > /sys/kernel/iommu_groups/<group id>/type
Fix above described issue by handling error path properly.
Reported-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
Cc: Jason Gunthorpe <jgg@ziepe.ca>
Tested-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
---
Changes in v2:
- Addressed review comments from Baolu
@Joerg,
This patch applies on top of iommu/next branch.
-Vasant
drivers/iommu/iommu.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 9e0228ef612b..e74e45f42c75 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -2915,10 +2915,15 @@ static int iommu_setup_default_domain(struct iommu_group *group,
}
}
+ if (old_dom)
+ iommu_domain_free(old_dom);
+ return ret;
+
err_restore:
if (old_dom) {
__iommu_group_set_domain_internal(
group, old_dom, IOMMU_SET_DOMAIN_MUST_SUCCEED);
+ group->default_domain = old_dom;
iommu_domain_free(dom);
old_dom = NULL;
}
--
2.31.1
next reply other threads:[~2023-06-19 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 8:49 Vasant Hegde [this message]
2023-06-19 11:31 ` [PATCH v2 iommu/next] iommu: Fix default domain setup Jason Gunthorpe
2023-06-20 5:11 ` Vasant Hegde
2023-06-20 6:31 ` Baolu Lu
2023-06-20 11:42 ` Jason Gunthorpe
2023-06-22 4:59 ` Vasant Hegde
2023-06-22 13:55 ` Jason Gunthorpe
2023-06-23 3:08 ` Baolu Lu
2023-06-23 4:38 ` 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=20230619084945.6427-1-vasant.hegde@amd.com \
--to=vasant.hegde@amd.com \
--cc=baolu.lu@linux.intel.com \
--cc=dheerajkumar.srivastava@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=suravee.suthikulpanit@amd.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