linux-kernel - RE: [PATCH v1 4/4] iommu: Notify requesters of IOMMU fault failures

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MW3PR11MB4681FD69CC7DA5276BC68E798056A@MW3PR11MB4681.namprd11.prod.outlook.com>
Date: Wed, 16 Jul 2025 11:20:32 +0000
From: "Temerkhanov, Sergey" <sergey.temerkhanov@...el.com>
To: Jason Gunthorpe <jgg@...pe.ca>
CC: "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "David
 Woodhouse" <dwmw2@...radead.org>, Lu Baolu <baolu.lu@...ux.intel.com>, "Joerg
 Roedel" <joro@...tes.org>, Will Deacon <will@...nel.org>, Robin Murphy
	<robin.murphy@....com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: RE: [PATCH v1 4/4] iommu: Notify requesters of IOMMU fault failures

> Look at how iommufd already associates faults back to its own struct device
> structure side-structure.
> 
> I think all you want for this problem is a way to hook the fault callback chain
> on a domain, and that should be local to the domain not global to the device..
> 

Moving this to a domain sounds reasonable, however the main goal is to reuse the kernel
SVA IOPF handling code to the maximum extent and only provide "feedback" when
iommu_sva_handle_iopf() returns an error for some reason.

Regards,
Sergey