[roll] Roll fuchsia [netsvc] Avoid double close Introduction of `Abort` in I8cee4203ba2cafaecd3776a5f0c55854dc199a0a introduced a race in freeing resources due to double call to Close. - Remove Close call from Abort, it's unnecessary since FileApi does that for us. - Replace refcount with a reference mask to avoid double close being a problem in the future. - Fix a race with Abort where workers should always reset the signal before observing the aborted bit, guaranteeing that we can't race with the `Abort` function setting the signal. - Introduce unit test that exercises the possible double close followed by a crash. - Introduce test that hits the Abort race mentioned above. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/638381 Original-Revision: bca62842fa938bbb3c7c5020852009ab48cf9287 GitOrigin-RevId: 679af286d8845ecb7da06153e66ccd6ce3f5ac41 Change-Id: I14b42c84b75ac241d3327ac526b55297c51b5afa
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 via the IRC channel #fuchsia on Freenode.
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.