linux-kernel - Re: [PATCH RESEND v2 3/4] iommu/riscv: Introduce IOMMU page table lock

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

Message-ID: <20250401151951.GG186258@ziepe.ca>
Date: Tue, 1 Apr 2025 12:19:51 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Xu Lu <luxu.kernel@...edance.com>
Cc: akpm@...ux-foundation.org, jhubbard@...dia.com,
	kirill.shutemov@...ux.intel.com, tjeznach@...osinc.com,
	joro@...tes.org, will@...nel.org, robin.murphy@....com,
	lihangjing@...edance.com, xieyongji@...edance.com,
	linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH RESEND v2 3/4] iommu/riscv: Introduce IOMMU page table
 lock

On Tue, Mar 18, 2025 at 11:59:29AM +0800, Xu Lu wrote:
> Introduce page table lock to address competition issues when modifying
> multiple PTEs, for example, when applying Svnapot. We use fine-grained
> page table locks to minimize lock contention.

This does not seem right, there is no need for locks to manage a cont
bit on the iommu side.

Jason