[roll] Roll fuchsia [usb][ddk] Fix async_remove after child release

In a few places, a parent device would call DdkAsyncRemove on a child
device manually in its unbind hook (or as part of a worker thread) after
the child device has already been released. This leads to a use after
free as the compat::Device backing the zx_device pointer is no longer
available. This change removes unnecessary DdkAsyncRemove calls directly
from the DdkUnbind hook, and also removes Refptr references in a
child_pre_release hook.

Multiply: ftdi-integration-test

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/975196
Original-Revision: dec325972feadc795f67fd8c34474fbab5329279
GitOrigin-RevId: 08547f6b1a2aa29447d99ea54babf7a2ae80a7b9
Change-Id: Ifab5ed88445fd3722352aea1b458a1b14ad2eb0b
1 file changed
tree: 032bf0b9382b9bbcd7ac3a9bd04e245627862f70
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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 via the IRC channel #fuchsia on Freenode.

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.