[roll] Roll fuchsia [netstack3] Support routine control flow

Support the Jump and Return actions in fuchsia.net.filter that allow
filtering routines to jump to uninstalled routines or return to the
calling routine.

This change also clarifies the difference between Accept and Return. All
routines evaluate to a final Return action by default, meaning that they
allow execution to continue in the calling routine (or to other routines
in the same hook). The default verdict for an entire hook is Accept.
When an Accept action is triggered within a routine, this action is
propagated all the way to the installed chain from which it was reached,
and execution continues at the next chain installed in the same hook (if
any).

Original-Fixed: 318718273
Test: netstack3-filter-test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1016954
Original-Revision: e0c990377ff58c666212ad2b8775c842384d5247
GitOrigin-RevId: 595be622ed1866172b402a35d9bdd1ae74bc4188
Change-Id: I6c579bb83f27a8b69d3753e5f2fd233758910865
1 file changed
tree: 54c371d8abaf2a1b1688ada46965b5d6bc52b046
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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 via the IRC channel #fuchsia on Freenode.

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.