[roll] Roll fuchsia [usb-rs] Manage buffer lifecycles correctly

The previous code unsafely leaked pointers to the reaper thread for the
buffers. Now URBs each have their own associated buffer which is tied to
their lifecycle.

Also we now try to cancel URBs when the waiting future is dropped.

There's still a chance that the reaper thread could successfully reap a
URB but the future could be gone already, in which case the data in the
buffer will be lost. So there's one more potential bug to squash.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1236764
Original-Revision: 5a3821f861d71a4b776555bce0a4014af2a644de
GitOrigin-RevId: 0e4c74622095c7e8d189f100fc846f63fccc7ad2
Change-Id: I158d76940a64a51cd6a2f0e09a6cf52a069d50b0
1 file changed
tree: 65f3f7ec2b38774aacbf06bfaee621fda731e2a6
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.