linux-kernel - RE: [PATCH v4 28/28] vfio/xe: Add device specific vfio

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: <BN9PR11MB52768BF0A4E6FA1B234E33108CC0A@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Sat, 8 Nov 2025 01:05:55 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Jason Gunthorpe <jgg@...pe.ca>
CC: "Winiarski, Michal" <michal.winiarski@...el.com>, Alex Williamson
	<alex@...zbot.org>, "De Marchi, Lucas" <lucas.demarchi@...el.com>,
	Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@...el.com>, Yishai Hadas <yishaih@...dia.com>,
	Shameer Kolothum <skolothumtho@...dia.com>, "intel-xe@...ts.freedesktop.org"
	<intel-xe@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"Brost, Matthew" <matthew.brost@...el.com>, "Wajdeczko, Michal"
	<Michal.Wajdeczko@...el.com>, "dri-devel@...ts.freedesktop.org"
	<dri-devel@...ts.freedesktop.org>, Jani Nikula <jani.nikula@...ux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, Tvrtko Ursulin
	<tursulin@...ulin.net>, David Airlie <airlied@...il.com>, Simona Vetter
	<simona@...ll.ch>, "Laguna, Lukasz" <lukasz.laguna@...el.com>, "Christoph
 Hellwig" <hch@...radead.org>, "Cabiddu, Giovanni"
	<giovanni.cabiddu@...el.com>, Brett Creeley <brett.creeley@....com>
Subject: RE: [PATCH v4 28/28] vfio/xe: Add device specific vfio_pci driver
 variant for Intel graphics

> From: Jason Gunthorpe <jgg@...pe.ca>
> Sent: Saturday, November 8, 2025 8:48 AM
> 
> On Fri, Nov 07, 2025 at 03:10:33AM +0000, Tian, Kevin wrote:
> > > To me, it looks like something generic, that will have impact on any
> > > device specific driver variant.
> > > What am I missing?
> > >
> > > I wonder if drivers that don't implement the deferred reset trick were
> > > ever executed with lockdep enabled.
> > >
> >
> > @Jason, @Yishai, @Shameer, @Giovanni, @Brett:
> >
> > Sounds it's a right thing to pull back the deferred reset trick into
> > every driver. anything overlooked?
> 
> It does seem like we should probably do something in the core code to
> help this and remove the duplication.

from backport p.o.v. it might be easier to first fix each driver 
independently then remove the duplication in upstream? 

> 
> I guess it makes sense the read/write lock would become entangled too.
> 

looks so