From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Eric Badger <ebadger@purestorage.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v2 0/2] iommu: Fix domain check on release (part 1/2)
Date: Thu, 29 Feb 2024 17:46:11 +0800 [thread overview]
Message-ID: <20240229094613.121575-1-baolu.lu@linux.intel.com> (raw)
This is a follow-up to the discussion thread here:
https://lore.kernel.org/linux-iommu/20240221154012.GC13491@ziepe.ca/
It fixes a NULL pointer dereference issue in the Intel iommu driver and
strengthens the iommu core to possibly prevent similar failures in other
iommu drivers.
There are two parts of this topic:
[x] Introduce release_domain and fix a kernel NULL pointer dereference
issue in the intel iommu driver.
[ ] A follow-up series to cleanup intel iommu driver.
Best regards,
baolu
Change log:
v2:
- The scalable mode context entry should be removed in the release path
as it's not part of the blocking domain.
v1: https://lore.kernel.org/linux-iommu/20240223051302.177596-1-baolu.lu@linux.intel.com/
Lu Baolu (2):
iommu: Add static iommu_ops->release_domain
iommu/vt-d: Fix NULL domain on device release
include/linux/iommu.h | 1 +
drivers/iommu/intel/pasid.h | 1 +
drivers/iommu/intel/iommu.c | 31 +++-----------
drivers/iommu/intel/pasid.c | 83 +++++++++++++++++++++++++++++++++++++
drivers/iommu/iommu.c | 19 +++++++--
5 files changed, 106 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-29 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:46 Lu Baolu [this message]
2024-02-29 9:46 ` [PATCH v2 1/2] iommu: Add static iommu_ops->release_domain Lu Baolu
2024-02-29 9:46 ` [PATCH v2 2/2] iommu/vt-d: Fix NULL domain on device release Lu Baolu
2024-03-04 7:36 ` Tian, Kevin
2024-03-04 8:07 ` Baolu Lu
2024-03-04 8:59 ` Tian, Kevin
2024-03-04 9:39 ` 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=20240229094613.121575-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ebadger@purestorage.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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