Received-SPF: pass (google.com: domain of linux-kernel+bounces-91199-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Feedback-ID: iac594737:Fastmail
Date: Mon, 4 Mar 2024 15:01:51 -0500
From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: linux-usb@vger.kernel.org
Cc: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= <marmarek@invisiblethingslab.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: usbip doesn't work with userspace code that accesses USB devices
Message-ID: <ZeYov0k8njwcZzGX@itl-email>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="omYEQKG3r4GVCydy"
Content-Disposition: inline


--omYEQKG3r4GVCydy
Content-Type: text/plain; protected-headers=v1; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Date: Mon, 4 Mar 2024 15:01:51 -0500
From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: linux-usb@vger.kernel.org
Cc: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= <marmarek@invisiblethingslab.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: usbip doesn't work with userspace code that accesses USB devices

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/57ab3940d450=
b18e570da57886d65cb5707aa60f
[3]: https://github.com/QubesOS/qubes-app-linux-usb-proxy/blob/57ab3940d450=
b18e570da57886d65cb5707aa60f/src/usb-export
[4]: https://github.com/QubesOS/qubes-app-linux-usb-proxy/blob/57ab3940d450=
b18e570da57886d65cb5707aa60f/src/usb-import
--=20
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

--omYEQKG3r4GVCydy
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmXmKL8ACgkQsoi1X/+c
IsEUCBAAvrO9zUYjf7lBdCcGpwQTWcfj1mmsdh5NKJF1RmfpmpuiZSoroJSfPtlF
19ZDl6srLOxQC7Mu0k3JQaJIBSiYY6C3kLEafYG40ftCemosKBrK7z/hYcmNz2ZW
wrrCO8ofcejvClFDjE89OP8KYD7/8SZpoB5rEr9mTxTFJyuwywUzT7dhCvQwNdu2
oE9YUh2q43ENzcVgEydceRBZa8ELas+gqQ8oK0PSPR8cmhic9TjhkfHXvzgqzvR1
t6pvs66quWK/BtaEMoW4gZN2+a2YZtimkaRIrngLYGDh+7zTPbyMp1rFVebgamAG
qeFTtRTyFqkb4NUlDr+pDk8BbbpYJOS/HPiYWXHvx3zl/1m+FJkrF9pA1dg5Z1Jn
eLzOJhHRcWeONu/m9Ic3Aunim4tggTCFktqtAj0P9RmuRiGhSs298SArhGbm3rHB
8NpJKlzpz9C2rberQsxwvtuzWmS1tOyMmjhfb+REzI4BEaRWG57eamfztD6TzYbD
TgmK4lP5rNlZjge4T1mUF4rcOPEMbCX7b0jbuqBseBBB7vSxhMCGhIlm2pIij+5g
/+6krJDBVQieNpyOBCmXhZDqcaf4717Bre+BiVUm6p9cl2VRRPwieTiWe9JMLwYr
40TbnuwS2nEox9AadwUQRzwhr/kt9dG7/4LCpHdhPrDQeTiiZk8=
=OKcn
-----END PGP SIGNATURE-----

--omYEQKG3r4GVCydy--