linux-kernel - Re: [PATCH v3 1/8] driver core: add a faux bus for use when a simple device/bus is needed

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: <2025020748-savings-porthole-9e27@gregkh>
Date: Fri, 7 Feb 2025 10:13:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Lyude Paul <lyude@...hat.com>
Cc: Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
	linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Danilo Krummrich <dakr@...nel.org>,
	Alexander Lobakin <aleksander.lobakin@...el.com>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Liam Girdwood <lgirdwood@...il.com>, Lukas Wunner <lukas@...ner.de>,
	Mark Brown <broonie@...nel.org>,
	Maíra Canal <mairacanal@...eup.net>,
	Robin Murphy <robin.murphy@....com>,
	Simona Vetter <simona.vetter@...ll.ch>,
	Zijun Hu <quic_zijuhu@...cinc.com>, linux-usb@...r.kernel.org,
	rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v3 1/8] driver core: add a faux bus for use when a simple
 device/bus is needed

On Thu, Feb 06, 2025 at 03:07:59PM -0500, Lyude Paul wrote:
> On Thu, 2025-02-06 at 19:08 +0100, Thomas Weißschuh wrote:
> > > +
> > > +	device_initialize(dev);
> > > +	dev->release = faux_device_release;
> > > +	dev->parent = &faux_bus_root;
> > 
> > I guess nobody will want to hang these off a different parent.
> 
> Oh - this is a good point that slipped my mind, how would we want to handle
> this case? The reason I ask is since we have things like
> drivers/gpu/drm/display/drm_dp_aux_dev.c which currently use the virtual
> device API but iirc do actually assign the DRM device owning the aux device as
> the parent.

Having a parent is fine, I just hadn't found any users of that yet.
I'll go add that option for v4.

thanks,

greg k-h