[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240229094613.121575-1-baolu.lu@linux.intel.com>
Date: Thu, 29 Feb 2024 17:46:11 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Jason Gunthorpe <jgg@...pe.ca>,
Kevin Tian <kevin.tian@...el.com>,
Eric Badger <ebadger@...estorage.com>
Cc: iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Lu Baolu <baolu.lu@...ux.intel.com>
Subject: [PATCH v2 0/2] iommu: Fix domain check on release (part 1/2)
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
Powered by blists - more mailing lists