linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Konovalov <andreyknvl@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>, Dmitry Vyukov <dvyukov@google.com>
Subject: Exporting USB device ids from the kernel
Date: Fri, 15 Nov 2019 15:25:38 +0100	[thread overview]
Message-ID: <CAAeHK+yyKeV8h6UO2-4zZM_ndUaHcG1Ex5GYHxdmh_GJxDOa4w@mail.gmail.com> (raw)

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].

I'm thinking of making a proper patch that will add a debugfs entry
like usb/drivers (and usb/hid_drivers?), that can be read to get
USB/HID device ids for all loaded drivers. Would that be acceptable?
Or should I use some other interface to do that?

Thanks!

[1] https://github.com/google/syzkaller/blob/master/tools/syz-usbgen/usb_ids.patch
[2] https://github.com/google/syzkaller/blob/master/sys/linux/init_vusb_ids.go
[3] https://github.com/google/syzkaller/blob/master/sys/linux/init_vusb.go

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 14:25 Andrey Konovalov [this message]
2019-11-15 15:06 ` Exporting USB device ids from the kernel Greg Kroah-Hartman
2019-11-15 15:13   ` Andrey Konovalov
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+yyKeV8h6UO2-4zZM_ndUaHcG1Ex5GYHxdmh_GJxDOa4w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).