[roll] Roll fuchsia [fuchsia-async] auditing locks in codebase duplicate function has a ghost handle. it's possible that a thread could lock the table, clone a handle, drop the lock. while thread b could lock the table, delete the handle. thread a continues and "successfully" duplicates a handle that was already closed. this cl fixes that scenario while also upholding memory safety Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1599789 Original-Revision: f84e46adf2cf36572edd15d340df17af2cebeb52 GitOrigin-RevId: 8d59daebb233f9b98e24d7ff909a6630d3afac14 Change-Id: Ie3510320c2a47d778ee39b3bd251b1d5100665f1
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.