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: <BN9PR11MB52768CB67C102CFCF562E8248C8CA@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Thu, 15 Jan 2026 05:59:56 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Baolu Lu <baolu.lu@...ux.intel.com>, Joerg Roedel <joro@...tes.org>, "Will
 Deacon" <will@...nel.org>, Robin Murphy <robin.murphy@....com>, "Jason
 Gunthorpe" <jgg@...dia.com>
CC: Dmytro Maluka <dmaluka@...omium.org>, Samiullah Khawaja
	<skhawaja@...gle.com>, "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] iommu/vt-d: Use 128-bit atomic updates for context
 entries

> From: Baolu Lu <baolu.lu@...ux.intel.com>
> Sent: Thursday, January 15, 2026 11:27 AM
> 
> On 1/14/26 15:54, Tian, Kevin wrote:
> >
> > Then this may be split into three patches:
> >
> > - change context_clear_entry() to be atomic, to fix the teardown path
> > - add present bit check in other functions in this patch, to scrutinize the
> >    attach path
> > - change those functions to be atomic, as a clean up
> 
> Perhaps this also paves the way for enabling hitless replace in the
> attach_dev path?
> 

I didn't get it. attach/replace are different paths and iommu core will
reject an attach request for a device which is already attached...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ