linux-kernel - [Patch Part2 V2 00/17] Enhance DMAR drivers to handle PCI/memory hotplug events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Feb 2014 14:07:20 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	Joerg Roedel <joro@...tes.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Yinghai Lu <yinghai@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Vinod Koul <vinod.koul@...el.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>
Cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Ashok Raj <ashok.raj@...el.com>,
	Yijing Wang <wangyijing@...wei.com>,
	Tony Luck <tony.luck@...el.com>,
	iommu@...ts.linux-foundation.org, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org
Subject: [Patch Part2 V2 00/17] Enhance DMAR drivers to handle PCI/memory hotplug events

Intel DMA/interrupt remapping drivers scan available PCI/memory devices
at startup and cache discovered hardware topologies. They don't update
cached information if PCI/memory hotplug event happens at runtime, then
the stale information may break DMA/interrupt remapping logic.

This patchset first (Patch 1-12) tries to introduces some helper
functions and fixes several bugs, then (Patch 13,14) uses a global
rwsem and RCU to protect global DMA/interrupt remapping data
structures, and finally (Patch 15-17) hook PCI/memory hotplug events
to update cached information.

It's also a preparation for supporting of DMA/interrupt remapping
hotplug.

V1->V2:
1) fix more bugs in dealing with identify mapping domain
2) address round 1 review comments

Jiang Liu (17):
  iommu/vt-d: avoid double free of g_iommus on error recovery path
  iommu/vt-d: avoid caching stale domain_device_info and fix memory
    leak
  iommu/vt-d: avoid caching stale domain_device_info when hot-removing
    PCI device
  iommu/vt-d: factor out dmar_alloc_dev_scope() for later reuse
  iommu/vt-d: move private structures and variables into intel-iommu.c
  iommu/vt-d: simplify function get_domain_for_dev()
  iommu/vt-d: free resources if failed to create domain for PCIe
    endpoint
  iommu/vt-d: reduce duplicated code to handle virtual machine domains
  iommu/vt-d: fix incorrect iommu_count for si_domain
  iommu/vt-d: check for NULL pointer when freeing IOMMU data structure
  iommu/vt-d: fix error in detect ATS capability
  iommu/vt-d: introduce macro for_each_dev_scope() to walk device scope
    entries
  iommu/vt-d: introduce a rwsem to protect global data structures
  iommu/vt-d: use RCU to protect global resources in interrupt context
  iommu/vt-d, PCI: update DRHD/RMRR/ATSR device scope caches when PCI
    hotplug happens
  iommu/vt-d, PCI: unify the way to process DMAR device scope array
  iommu/vt-d: update IOMMU state when memory hotplug happens

 drivers/iommu/dmar.c                |  412 +++++++++++++------
 drivers/iommu/intel-iommu.c         |  750 ++++++++++++++++++-----------------
 drivers/iommu/intel_irq_remapping.c |  108 +++--
 drivers/iommu/iova.c                |   64 ++-
 include/linux/dmar.h                |   74 ++--
 include/linux/iova.h                |    2 +
 6 files changed, 848 insertions(+), 562 deletions(-)

-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/