)]}'
{
  "commit": "c0b362d177cefb35eed02f5862ce0632585c4e96",
  "tree": "032bf0b9382b9bbcd7ac3a9bd04e245627862f70",
  "parents": [
    "f7c1577a2f11aa176dfe5ae06095ae1ceceead6e"
  ],
  "author": {
    "name": "Novin Changizi",
    "email": "novinc@fuchsia.infra.roller.google.com",
    "time": "Fri Jan 19 02:01:41 2024 +0000"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Jan 18 18:02:53 2024 -0800"
  },
  "message": "[roll] Roll fuchsia [usb][ddk] Fix async_remove after child release\n\nIn a few places, a parent device would call DdkAsyncRemove on a child\ndevice manually in its unbind hook (or as part of a worker thread) after\nthe child device has already been released. This leads to a use after\nfree as the compat::Device backing the zx_device pointer is no longer\navailable. This change removes unnecessary DdkAsyncRemove calls directly\nfrom the DdkUnbind hook, and also removes Refptr references in a\nchild_pre_release hook.\n\nMultiply: ftdi-integration-test\n\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/975196\nOriginal-Revision: dec325972feadc795f67fd8c34474fbab5329279\nGitOrigin-RevId: 08547f6b1a2aa29447d99ea54babf7a2ae80a7b9\nChange-Id: Ifab5ed88445fd3722352aea1b458a1b14ad2eb0b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "411a78bed33f90e697ad3810d23b503aaa2b40eb",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "781c7ef101e8d8e7c08e96eb495cd5ca000ac47d",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}