[roll] Roll fuchsia [netstack3] Fix panic with out-of-order SACK block Address a panic that can happen when we put ourselves in a bad state by wrongfully processing an ack segment whose ACK number is before the tracked SND.UNA and placing its SACK blocks in the scoreboard. Address by ignoring all ACKs before SND.UNA and add a regression test. While I'm here, address another possible panic in the Rule 4 implementation for SACK recovery when SND.NXT is rewound. Original-Fixed: 409599338 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1249108 Original-Revision: 5a70c25b093e2e17ee11cb1f643fd7a98ab3218c GitOrigin-RevId: c08d8d69e98e23107013584f4426ab269dd5f011 Change-Id: I17a192795521b3ad45febd0ef0cbce9c9f1e199a
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.