[roll] Roll fuchsia [netstack3] Use fasync::Scope for route sets

Use an fasync::Scope for route sets so we can join on them and ensure
route sets are no longer being served by the time the parent route table
is removed.

This can also be used to propagate down the shutdown signal for clean
shutdown with route sets.

While I'm here, extract a common helper for spawning route sets and
rework the route table serving to make sure the route table is removed
if FIDL errors are observed while serving a non-detached route table.

Original-Bug: 380897722
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1256905
Original-Revision: acaa8eda9d4ba7f99390e2f657d2c8d0d233d946
GitOrigin-RevId: c4594d02cbb23a81d3787794f56323b5390bf009
Change-Id: Ieb77a29491d07444bf704e980acd341247829bc5
1 file changed
tree: c983935f96bfaaaff5f0fcbd127fb76b6f88d604
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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 in one of the communication channels documented at get involved.

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.