[roll] Roll fuchsia [netstack3] Don't allow 2 TCP connections with the same 4-tuple.

This situation is now possible because we now have SO_REUSEADDR: one
client can try to bind to the same local ip/port, but then when it tries
to connect to a remote peer, if that results in a 4-tuple that's the
same as some existing connections, the connect attempt should fail.

Original-Fixed: 127164
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/856876
Original-Revision: 52b9176f95785c941eb999629ac369d3f3302523
GitOrigin-RevId: 40f6751cfb8872bac6e55e6a994c9f2f6dcfccb7
Change-Id: Ie2b6709fa3d350dde3d6cde7abd74ce6100492a0
1 file changed
tree: 347f8828e00ce3674ee631ff663ad6612257a8a2
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.