src/lib/libusb, branch releng/13.5FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F13.52025-01-07T09:03:21Zlibusb: fix hotplug sigbus2025-01-07T09:03:21ZBaptiste Daroussinbapt@FreeBSD.org2025-01-03T09:50:30Zurn:sha1:eb9fa4c2d786b327bb4d9bd7727428c70a33c710
When a hotplug callback has been registered, and the program using
libusb is calling libusb_exit then the thread handler is set to
NO_THREAD which result in the variable controlling the loop the be set
to 0, it does a last pass through device available without having done
a scan, which result in a sigbus after it tried to unregister all the
devices.
directly break the loop instead and cleanup the list of devices
this fixes the tests with LGPLed libusb's hotplugtest program
MFC After: 3 days
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D48298
(cherry picked from commit ba5834b8e11fd002a663d083a464e397e76cb3a9)
libusb: claim to be version 1.0.162024-08-06T21:52:37ZEd Masteemaste@FreeBSD.org2024-06-06T13:33:44Zurn:sha1:02ef8e4061abc0a0fc148a8e41efde46fde0d5b0
We are not 100% compatible with 1.0.16, but implement some
functionality from that version that is required by certain ports.
PR: 277799
PR: 279555 (exp-run)
Event: Kitchener-Waterloo Hackathon 202406
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D45514
(cherry picked from commit 5654b42142e1f689b26d405c90379b85f22349a0)
(cherry picked from commit 5bd6e6c1ddff7f10e8b86703536d81af8ce0532b)
Remove $FreeBSD$: two-line nroff pattern2023-08-23T17:43:31ZWarner Loshimp@FreeBSD.org2023-08-22T01:32:08Zurn:sha1:b144e70a3325e033163aa4e6e15d0446e245702d
Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/
Similar commit in main:
(cherry picked from commit fa9896e082a1)
Remove $FreeBSD$: one-line sh pattern2023-08-23T17:43:30ZWarner Loshimp@FreeBSD.org2023-08-22T01:32:01Zurn:sha1:023fc80ee38a117fa65b2ccb2abf8bdc7dbd6fd9
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Similar commit in main:
(cherry picked from commit d0b2dbfa0ecf)
Remove $FreeBSD$: one-line .c comment pattern2023-08-23T17:43:23ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:18Zurn:sha1:8ad303d68cec3ee1133550de37e0009502621e50
Remove /^/[*/]\s*\$FreeBSD\$.*\n/
Similar commit in main:
(cherry picked from commit 2a63c3be1582)
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD2023-07-25T15:13:49ZWarner Loshimp@FreeBSD.org2023-05-10T15:40:58Zurn:sha1:caa41f641755c935b036e17440a3b49329c904ed
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
(cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b)
libusb: remove use of COMPAT_32BIT2023-04-30T06:56:15ZBrooks Davisbrooks@FreeBSD.org2021-12-17T21:28:14Zurn:sha1:a03d9f2634664361fd7554a7e32f36e0a2131da3
This codepath used uint64_t's in place of pointers in structs and
arrays to allow 32-bit code to use 64-bit version of ioctls. Now
that we support 32-bit compat natively this is no longer needed.
Reviewed by: hselasky, jrtc27 (prior version)
(cherry picked from commit 8010f4ad21b6120e929bda4eed27696e63514677)
libusb(3): Implement libusb_init_context() and the needed structures and definitions.2023-04-30T06:56:15ZHans Petter Selaskyhselasky@FreeBSD.org2023-01-26T12:56:51Zurn:sha1:8ff5099a793207af0d6080b01df40392c3c5b51f
Differential Revision: https://reviews.freebsd.org/D38212
Sponsored by: NVIDIA Networking
(cherry picked from commit 4c6bcffd04f9d0b6cb57af0ffcc9be3098fe950c)
libusb(3): Implement libusb_interrupt_event_handler() by exposing existing function.2022-10-12T15:53:22ZHans Petter Selaskyhselasky@FreeBSD.org2022-10-02T15:30:40Zurn:sha1:e4e79af3f9573cbc2db5a8e96f42236d9921662f
Sponsored by: NVIDIA Networking
(cherry picked from commit aa87aa52326be7b726664dba65e91ec3d8160f48)
libusb(3): Ignore SIGPIPE when initializing the LibUSB v1.0 API.2022-03-05T14:40:08ZHans Petter Selaskyhselasky@FreeBSD.org2022-03-02T11:31:27Zurn:sha1:4340df3418ecea57b5e48dec94ac4b1d4f760aca
The LibUSB v1.0 emulation layer uses pipes internally to signal between
threads. When USB devices are reset, as part of loading firmware, SIGPIPE
may happen, and that is expected and should be ignored.
PR: 261891
Sponsored by: NVIDIA Networking
(cherry picked from commit d94d94e2c06b4331f706a3b4eca058041294ea05)