From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: linux-usb@vger.kernel.org
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: usbip doesn't work with userspace code that accesses USB devices
Date: Mon, 4 Mar 2024 15:01:51 -0500 [thread overview]
Message-ID: <ZeYov0k8njwcZzGX@itl-email> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Qubes OS users are reporting that MTP doesn't work with USB passthrough.
Fastboot (used for flashing a custom OS to an Android device) also
doesn't work. Kernel-mode drivers, such as Bluetooth and USB storage,
seem to usually work as expected. Since MTP and fastboot are both
implemented in userspace, it appears that there is some problem with the
interaction of usbip, our USB proxy (which is based on USBIP), and
userspace programs that interact with USB devices directly.
The bug report can be found at [1] and the source code for the USB proxy
can be found at [2]. The script used on the sending side (the one with
the physical USB controller) is at [3] and the script used by the
receiving side (the one the device is attached to) is at [4]. All of
these links are for the current version as of this email being sent, so
that anyone looking at this email in the future doesn't get confused.
Is this a bug in usbip, or is this due to usbip being used incorrectly?
I'm happy to provide additional information needed to debug the problem,
but I don't have access to the reporter's system.
[1]: https://github.com/QubesOS/qubes-issues/issues/6330
[2]: https://github.com/QubesOS/qubes-app-linux-usb-proxy/tree/57ab3940d450b18e570da57886d65cb5707aa60f
[3]: https://github.com/QubesOS/qubes-app-linux-usb-proxy/blob/57ab3940d450b18e570da57886d65cb5707aa60f/src/usb-export
[4]: https://github.com/QubesOS/qubes-app-linux-usb-proxy/blob/57ab3940d450b18e570da57886d65cb5707aa60f/src/usb-import
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-03-04 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 20:01 Demi Marie Obenour [this message]
2024-03-04 21:04 ` usbip doesn't work with userspace code that accesses USB devices Greg KH
2024-03-04 22:46 ` Marek Marczykowski-Górecki
2024-03-04 23:52 ` Marek Marczykowski-Górecki
2024-03-05 0:06 ` Demi Marie Obenour
2024-03-05 0:33 ` Marek Marczykowski-Górecki
2024-03-05 3:19 ` Alan Stern
2024-03-05 18:03 ` Demi Marie Obenour
2024-03-04 22:58 ` Demi Marie Obenour
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=ZeYov0k8njwcZzGX@itl-email \
--to=demi@invisiblethingslab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
/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