[roll] Roll fuchsia [zircon][port] Check if port observer is canceled in MaybeReap When considering whether to reap a matched port observer in PortDispatcher::MaybeReapLocked, we have to consider the case that another thread has canceled the observe and removed it from the PortDispatcher's observer_ list into a local list for cleanup. In this case, the PortPacket will be marked as canceled (guarded by the PortDispatcher lock) but may still be live in the dispatcher's observer list. We can skip these in the thread calling MaybeReap as we know that another thread is already performing cleanup work. The added core test hits this case reliably with --count=10 running in x86_64 under KVM emulation. Original-Fixed: 502262595 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1574215 Original-Revision: a47231d96cbfecf64911b138f350429d1d856056 GitOrigin-RevId: 0fa654c2560f153a97ad9ef4a9f9b6ddce90150a Change-Id: I1c2d2881ace4e60574f136d21aa073c049e018ba
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.