[roll] Roll fuchsia [netstack3][tcp] Allow same 4-tuple but different devices Before this change, the TCP demuxer only allows connections with unique 4-tuples, this is stricter than it needs be on a system with multiple network interfaces: connections should be able to coexist with unique 5-tuples. In reality, it is possible that two hosts with the same link-local addrs exist on the two networks that we are connected to through different interfaces. If the 2 hosts both try to establish a connection with us, the second one is rejected and trips an invariant assertion in the demux code. Instead of relaxing the invariant assertion, which could allow other types of bugs without us noticing, we allow such connections to be created on the system as long as the 5-tuple is unique. It is not changed that 2 connections still conflict with each other if both of them have the same 4-tuple but one has a device bound while the other is not. Original-Fixed: 475191687, 321240038 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1477438 Original-Revision: 64a730cc3a1b7c49aa030cd3d1564440aeed1dd0 GitOrigin-RevId: 5b4223dfa6ddc55d2bf93a125022d788c8ac974a Change-Id: I29005838391df22875fc2bf016524e1b1da6c4d4
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 in one of the communication channels documented at get involved.
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.