linux-kernel - Re: [PATCH v2] iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases

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

Message-ID: <176408432658.533561.11326321438945922716.b4-ty@nvidia.com>
Date: Tue, 25 Nov 2025 11:26:11 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: will@...nel.org,
	Nicolin Chen <nicolinc@...dia.com>
Cc: robin.murphy@....com,
	joro@...tes.org,
	kevin.tian@...el.com,
	praan@...gle.com,
	linux-arm-kernel@...ts.infradead.org,
	iommu@...ts.linux.dev,
	linux-kernel@...r.kernel.org,
	skolothumtho@...dia.com
Subject: Re: [PATCH v2] iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases


On Mon, 03 Nov 2025 09:27:55 -0800, Nicolin Chen wrote:
> A vDEVICE has been a hard requirement for attaching a nested domain to the
> device. This makes sense when installing a guest STE, since a vSID must be
> present and given to the kernel during the vDEVICE allocation.
> 
> But, when CR0.SMMUEN is disabled, VM doesn't really need a vSID to program
> the vSMMU behavior as GBPA will take effect, in which case the vSTE in the
> nested domain could have carried the bypass or abort configuration in GBPA
> register. Thus, having such a hard requirement doesn't work well for GBPA.
> 
> [...]

Applied, thanks!

[1/1] iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases
      https://git.kernel.org/jgg/iommufd/c/9f0b286fe40130

Best regards,
-- 
Jason Gunthorpe <jgg@...dia.com>