[roll] Roll fuchsia [netstack3] Move slaac to TimerContext2

Slaac is a bit overdue for a refactor, but it's more time than I can
spend right now. The best way to get rid of races in the SLAAC module is
to introduce its own lock level, and place a timer heap there. This
makes it easier to reason about Slaac serializing all its operations,
and this is fine because SLAAC is not on the fast path.

While I'm here, allow racing user address removal with the invalidate
timer expiration since we cannot guarantee synchronization.

Original-Bug: 42083407
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1032852
Original-Revision: 5e44af81d126a976ab4b343c8e7f46bcbdec7473
GitOrigin-RevId: 8170161154bbd8860c05411640d1a0869c9545d3
Change-Id: I905917f85287308dd913f9fc5fc97a4fcafc3c7c
1 file changed
tree: 0da0e96510ffacf09bb2cc3665aafb2efd7c2e9f
  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.