linux-kernel - Re: [PATCH 0/3] iommupt/vtd: Support dirty tracking on PASID

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20260206004325.GB943673@ziepe.ca>
Date: Thu, 5 Feb 2026 20:43:25 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Zhenzhong Duan <zhenzhong.duan@...el.com>
Cc: linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
	dwmw2@...radead.org, baolu.lu@...ux.intel.com, joro@...tes.org,
	will@...nel.org, robin.murphy@....com, kevin.tian@...el.com
Subject: Re: [PATCH 0/3] iommupt/vtd: Support dirty tracking on PASID

On Wed, Feb 04, 2026 at 09:34:01PM -0500, Zhenzhong Duan wrote:
> Hi,
> 
> When we add pasid support in QEMU for passthrough device, we found
> PASID attachment to a nested parent domain with dirty tracking failed.
> 
> It's because PASID-level dirty tracking is not there yet, by adding it,
> we can enable PASID attachment to such domain.
> 
> Thanks
> Zhenzhong
> 
> 
> Zhenzhong Duan (3):
>   iommupt/vtd: Pass dmar_domain pointer to device_set_dirty_tracking()
>   iommupt/vtd: Support dirty tracking on PASID
>   iommufd/selftest: Test dirty tracking on PASID

I'm not sure why you marked this s iommupt? It isn't right?

Also only the second stage table supports dirty tracking so I'm
confused what is the issue? Is it trying to say that if a second stage
is written to a pasid entry on a !=0 pasid path it doesn't work right?
But it does work on a 0 pasid?

Huh?

That sounds like a systemic problem, the two flows shouldn't actually
be any different.

Jason