libusb: do not freeze when device vanishs #5434
Comments
skalk
added a commit
to skalk/genode
that referenced
this issue
Jan 23, 2025
Instead of freezing, return corresponding libusb error code if the USB device got disconnected. Therefore, components using the library can continue to work otherwise. Fix genodelabs#5434
chelmuth
pushed a commit
that referenced
this issue
Jan 23, 2025
Instead of freezing, return corresponding libusb error code if the USB device got disconnected. Therefore, components using the library can continue to work otherwise. Fix #5434
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working on issue #5401 I was stumbling upon much error messages from our libusb port resp. binding, whenever the related USB device vanished. Therefore, I changed it to warn once and freeze. As it turned out: there are use-cases of this library, where a component using the libusb implements another service. When the USB device of this component vanishs, it shall get restarted, but first it's clients have to gracefully close their sessions to the component. Therefore, the component must not freeze in the first place, when the USB device vanishs.
Alternatively, we should propagate an appropriated error code of the libusb to the API clients.
The text was updated successfully, but these errors were encountered: