[roll] Roll fuchsia [netstack3] Move TCP to new TimerContext

Introduce CoreTimerContext in the base crate, which provides the new
timer-transformation mechanism that ties in with the new timer context.

Use the fact that we now need a type to control timers to provide
type-safety around the fact that only connected TCP sockets have timers,
which is a nice side-effect.

While I'm here, we've identified a race with tw reuse that can happen
between the reuse and timewait state timers firing. Relax the timer
handler and timer cancelation to deal with that.

Original-Bug: 42083407
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1009218
Original-Revision: 4c9b443b2aed103da5d8306c39987d81f17e9fe1
GitOrigin-RevId: f1d4d01816296b791ab3a1301d734282497c8329
Change-Id: I5bb8043fb0823d9982c27b9b23134eff0efacc36
1 file changed
tree: 563f8cc85fa6c42600a26462738fee26ea04dd39
  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.