From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Extending USB_CONNECTINFO ioctl
Date: Mon, 3 Jun 2019 17:24:10 -0700 [thread overview]
Message-ID: <20190604002410.GA36666@dtor-ws> (raw)
Hi Alan, Greg,
When running software in a jailed environment where sysfs or udev is not
readily available and one can only have an FD to usbdevfs device passed
into the jail, there is a desire to allow libusb working. Alan recently
added USBDEVFS_GET_SPEED, but we are still missing bus number and list
of port numbers on the way to the root to be able to better identify the
device in question.
What do you think about adding a new ioctl:
struct usbdevfs_connectinfo_ex {
__u32 size; /* size of the structure from the kernel POV */
__u32 busnum;
__u32 devnum;
__u32 speed; /* USB_SPEED_* form ch9.h */
u8 num_ports; /* Number of entries in port_numbers array */
u8 port_numbers[31]; /* Current limit in USB3.0 spec is 7 */
};
/*
* Returns struct usbdevfs_connectinfo_ex; length is variable to allow
* extending size of the data returned.
*/
#define USBDEVFS_CONNINFO_EX(len) _IOC(_IOC_READ, 'U', 32, len)
Thanks.
--
Dmitry
next reply other threads:[~2019-06-04 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 0:24 Dmitry Torokhov [this message]
2019-06-04 5:38 ` Extending USB_CONNECTINFO ioctl Greg Kroah-Hartman
2019-06-04 14:17 ` Alan Stern
2019-06-04 16:14 ` Dmitry Torokhov
2019-06-04 16:48 ` Greg Kroah-Hartman
2019-06-10 22:31 ` Dmitry Torokhov
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=20190604002410.GA36666@dtor-ws \
--to=dmitry.torokhov@gmail.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).