All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Konovalov <andreyknvl@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	USB list <linux-usb@vger.kernel.org>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: Exporting USB device ids from the kernel
Date: Fri, 15 Nov 2019 16:13:58 +0100	[thread overview]
Message-ID: <CAAeHK+zdZdDT=3nNaz3E3HoUVq+sUA5hKEpOTXu7faitJ6RCGw@mail.gmail.com> (raw)
In-Reply-To: <20191115150633.GA374386@kroah.com>

On Fri, Nov 15, 2019 at 4:06 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Fri, Nov 15, 2019 at 03:25:38PM +0100, Andrey Konovalov wrote:
> > Hi Greg and Alan,
> >
> > For USB fuzzing it would be nice to be able to export usb_device_id
> > structs from the kernel to facilitate the fuzzer with generating USB
> > descriptors that match to actual drivers. The same is required for
> > hid_device_id structs, since those are matched separately by the
> > usbhid driver (are there other cases like this?).
> >
> > Currently I have a hacky patch [1] that walks all drivers for USB and
> > HID buses and then prints all device ids for those drivers into the
> > kernel log. Those are manually parsed and built into the fuzzer [2]
> > and then used to generate USB descriptors [3].
>
> The kernel will spit out all device ids of all USB devices when found if
> you have CONFIG_USB_ANNOUNCE_NEW_DEVICES enabled, if you want to parse
> the log.
>
> Otherwise, just walk usbfs or sysfs and get the ids there.  If you use
> libusb you can do this with just a few lines of code, or worst case,
> just implement the same thing on your own (like lsusb used to do).
> Heck, just copy what lsusb does, or again worst case, parse the output
> of it.
>
> There's also 'lsusb.py' as part of usbutils that shows how to do this
> from within python in userspace, and if you really want it, we also
> export the whole raw usb descriptor is in sysfs as well, if you want to
> not trust how the kernel parses it.
>
> hope this helps,

Either I misunderstand you or you misunderstood me. I don't want to
see IDs of devices that are connected. I want to see all of the IDs
for all of the devices that might be connected and bound to some
driver at some point in the future. Essentially I want to all IDs that
are passed to MODULE_DEVICE_TABLE(usb, ...) and
MODULE_DEVICE_TABLE(hid, ...). Is it possible to obtain those via
usbfs/sysfs?

  reply	other threads:[~2019-11-15 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 14:25 Exporting USB device ids from the kernel Andrey Konovalov
2019-11-15 15:06 ` Greg Kroah-Hartman
2019-11-15 15:13   ` Andrey Konovalov [this message]
2019-11-15 15:30     ` Greg Kroah-Hartman
2019-11-15 15:44 ` Alan Stern
2019-11-15 16:10   ` Andrey Konovalov
2019-11-16  8:48     ` Greg Kroah-Hartman
2019-11-18 16:12       ` Andrey Konovalov
2019-11-18 16:39         ` Greg Kroah-Hartman
2019-11-18 17:42           ` Andrey Konovalov
2019-11-18 17:57             ` Greg Kroah-Hartman
2019-12-02 16:19               ` Andrey Konovalov
2019-12-02 16:49                 ` Greg Kroah-Hartman
2019-12-03 13:47                   ` Andrey Konovalov
2020-01-13 14:48               ` Andrey Konovalov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAeHK+zdZdDT=3nNaz3E3HoUVq+sUA5hKEpOTXu7faitJ6RCGw@mail.gmail.com' \
    --to=andreyknvl@google.com \
    --cc=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.