iommu/vt-d: Make DMA-fault page-table dump user-selectable
Subsystems (2)
PATCH 1/1 iommu/vt-d: Make DMA-fault page-table dump user-selectable
From: Ahmed Abdelraoof <[email protected]>
The page-table dump was gated behind the hidden CONFIG_DMAR_DEBUG symbol, only reachable by enabling the full INTEL_IOMMU_DEBUGFS interface. That interface is explicitly flagged as not for production and exposes far more IOMMU internals than a fault dump needs, so there was no way to get this diagnostic from menuconfig on production kernel without taking on the rest.
This patch renames it to CONFIG_DMAR_FAULT_DEBUG with a prompt and help text so the fault dump can be enabled on its own, and updates all references in iommu.c and dmar.h. INTEL_IOMMU_DEBUGFS still selects it, so existing configs are unaffected; no functional change otherwise.
--- drivers/iommu/intel/Kconfig | 11 ++++++++--- drivers/iommu/intel/iommu.c | 2 +- include/linux/dmar.h | 2 +- 3 files changed, 10 insertions(+), 5 deletions(-)
drivers/iommu/intel/Kconfig +8 -3
@@ -6,8 +6,13 @@ config DMAR_TABLE config DMAR_PERF bool -config DMAR_DEBUG - bool +config DMAR_FAULT_DEBUG + bool "Dump Intel IOMMU page tables on DMA fault" + depends on INTEL_IOMMU + help + On a DMA Remapping (DMAR) fault, walk the Root / Context / + PASID / second-level page-table entries for the faulting + source-id and IOVA and emit them via pr_info. config INTEL_IOMMU bool "Support for Intel IOMMU using DMA Remapping Devices"
@@ -39,7 +44,7 @@ config INTEL_IOMMU_DEBUGFS bool "Export Intel IOMMU internals in Debugfs" depends on IOMMU_DEBUGFS select DMAR_PERF - select DMAR_DEBUG + select DMAR_FAULT_DEBUG help !!!WARNING!!!
drivers/iommu/intel/iommu.c +1 -1
@@ -549,7 +549,7 @@ static void free_context_table(struct intel_iommu *iommu) iommu->root_entry =NULL ; } -#ifdef CONFIG_DMAR_DEBUG +#ifdef CONFIG_DMAR_FAULT_DEBUG static void pgtable_walk (struct intel_iommu *iommu,unsigned long pfn,u8 bus,u8 devfn,struct dma_pte *parent,int level) {
include/linux/dmar.h +1 -1
@@ -126,7 +126,7 @@ static inline int dmar_res_noop(struct acpi_dmar_header *hdr, void *arg)return 0 ; } -#ifdef CONFIG_DMAR_DEBUG +#ifdef CONFIG_DMAR_FAULT_DEBUG void dmar_fault_dump_ptes (struct intel_iommu *iommu,u16 source_id,unsigned long long addr,u32 pasid);#else
Signature · 12 lines
2.47.3 Amazon Web Services Development Center Germany GmbH Tamara-Danz-Str. 13 10243 Berlin Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B Sitz: Berlin Ust-ID: DE 365 538 597
Baolu Lu
maintainerQuoted 9 lines · Ahmed Abdelraoof
From: Ahmed Abdelraoof <[email protected]>
The page-table dump was gated behind the hidden
CONFIG_DMAR_DEBUGsymbol, only reachable by enabling the fullINTEL_IOMMU_DEBUGFSinterface. That interface is explicitly flagged as not for production and exposes far more IOMMU internals than a fault dump needs, so there was no way to get this diagnostic from menuconfig on production kernel without taking on the rest.
Quoted 4 lines
This patch renames it to
CONFIG_DMAR_FAULT_DEBUGwith a prompt and help text so the fault dump can be enabled on its own, and updates all references iniommu.canddmar.h.INTEL_IOMMU_DEBUGFSstill selects it, so existing configs are unaffected; no functional change otherwise.
pgtable_walk() is not safe or robust enough to expose in production environments; that is why it is currently limited to CONFIG_DMAR_DEBUG.
Intel IOMMU hardware walks multiple page-table formats. Some are managed by the IOMMU subsystem (iommupt), while others are shared with CPU page tables and managed outside the IOMMU subsystem. In the near future, there may also be page tables managed by the TDX module in private memory that the IOMMU driver cannot access.
Another issue is that pgtable_walk() lacks proper locking to protect against concurrent page-table updates. This makes it fragile and can potentially lead to UAF issues.
Quoted 55 lines
Signed-off-by Ahmed Abdelraoof <[email protected]>--- drivers/iommu/intel/Kconfig | 11 ++++++++--- drivers/iommu/intel/iommu.c | 2 +- include/linux/dmar.h | 2 +- 3 files changed, 10 insertions(+), 5 deletions(-)drivers/iommu/intel/Kconfig +8
-3@@ -6,8 +6,13 @@ config DMAR_TABLE config DMAR_PERF bool -config DMAR_DEBUG - bool +config DMAR_FAULT_DEBUG + bool "Dump Intel IOMMU page tables on DMA fault" + depends on INTEL_IOMMU + help + On a DMA Remapping (DMAR) fault, walk the Root / Context / + PASID / second-level page-table entries for the faulting + source-id and IOVA and emit them via pr_info. config INTEL_IOMMU bool "Support for Intel IOMMU using DMA Remapping Devices"@@ -39,7 +44,7 @@ config INTEL_IOMMU_DEBUGFS bool "Export Intel IOMMU internals in Debugfs" depends on IOMMU_DEBUGFS select DMAR_PERF - select DMAR_DEBUG + select DMAR_FAULT_DEBUG help !!!WARNING!!!drivers/iommu/intel/iommu.c +1
-1@@ -549,7 +549,7 @@ static void free_context_table(struct intel_iommu *iommu) iommu->root_entry =NULL ; } -#ifdef CONFIG_DMAR_DEBUG +#ifdef CONFIG_DMAR_FAULT_DEBUG static void pgtable_walk (struct intel_iommu *iommu,unsigned long pfn,u8 bus,u8 devfn,struct dma_pte *parent,int level) {include/linux/dmar.h +0
-0
include/linux/dmar.h static inline int dmar_res_noop(struct acpi_dmar_header *hdr, void *arg) · line 132
Quoted 8 lines
include/linux/dmar.h +1
-1@@ -126,7 +126,7 @@ static inline int dmar_res_noop(struct acpi_dmar_header *hdr, void *arg)return 0 ; } -#ifdef CONFIG_DMAR_DEBUG +#ifdef CONFIG_DMAR_FAULT_DEBUG void dmar_fault_dump_ptes (struct intel_iommu *iommu,u16 source_id,unsigned long long addr,u32 pasid);#else
Thanks,
baolu