| commit | 21acf2b021c1fb7e1e6b56ecde8fb8861f3b6e2a | [log] [tgz] |
|---|---|---|
| author | Peter DeLong <pdelong@fuchsia.infra.roller.google.com> | Tue Nov 05 20:25:54 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 05 12:31:49 2024 -0800 |
| tree | 43ed0c73136a8254994d1ca54af790f0790507ff | |
| parent | 079c4fa05ad0ed234f37dfa16f642c94cb4b2578 [diff] |
[roll] Roll fuchsia [netstack3] Enter ZWP on zero window update As written, if the window shrinks to 0, but no new data is acked, then the retransmit timer won't be cancelled. If there's a timer set, then Netstack3 doesn't enter ZWP. This leads to a situation where it continually tries to retransmit, but since the window is zero, it can't send any data. Original-Fixed: 377294231 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1150293 Original-Revision: 0b6b4f799d02fd14f43b11a6939dd914098b32ac GitOrigin-RevId: c095bec37b60fc489bfb1f0f519464060feb028e Change-Id: I8ed011d02ad2c153a3c580765147ecffa8fd9143
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.