[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
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.