linux-kernel - Re: [PATCH 1/2] usb: linux/usb.h: Move USB port definition to usb.h

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: <2024090522-suggest-overpay-9fba@gregkh>
Date: Thu, 5 Sep 2024 08:49:53 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc: hdegoede@...hat.com, ilpo.jarvinen@...ux.intel.com, jorge.lopez2@...com,
	acelan.kao@...onical.com, platform-driver-x86@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 1/2] usb: linux/usb.h: Move USB port definition to usb.h

On Thu, Sep 05, 2024 at 02:24:31PM +0800, Kai-Heng Feng wrote:
> On Thu, Sep 5, 2024 at 1:20 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> >
> > On Thu, Sep 05, 2024 at 12:24:46PM +0800, Kai-Heng Feng wrote:
> > > Move struct usb_port to linux/usb.h so other subsystems can use it too.
> >
> > These really are "internal to the usb core" functions and variables, I
> > am loath to export them as it requires that you "know" what the device
> > type is of something without any recorse if you get it wrong.  I
> > commented on patch 2/2 about that.
> >
> > Could we provide a usb core function for you instead to help out?  What
> > exactly are you trying to get access to on the USB bus that you need to
> > use here, the port or the device?
> 
> The device so the quirk can check its vendor and product id.
> 
> That means a function or helper that can return USB port/device from
> an ACPI path.

So you don't want the port, only the device.  Why not just search the
bus for a device, you don't care where in the acpi path it lives, right?
Or better yet, do this in the driver for the device itself, that's when
you know you have the right device.

thanks,

greg k-h