Hi Stefano, Anshu, Thanks! Yes, I would be happy to have a Reported-by tag. Happy to help! I tested v3 as sent on my laptop, using source revision 6aa4f88 and Linux 7.0.0-43. I used an extended version of the reproducer I uploaded to bug 224 (attachment 73), with added periodic ACKs, delayed ACKs, zero-window cases and retry timing measurements. With both directions open, dropping the first data segment stops causing a retransmission storm. If the segment remains missing, v3 retries after about two seconds. With a half-closed connection (the client sends FIN, then waits for the response), v3 also stops the storm. Two cases still fail when the client sends the same ACK every 10 ms: * If the missing segment is never accepted, there is no further retry during the four-second test. * If the client starts accepting that segment after 100 ms, there is still no retry, and the transfer does not complete within four seconds. Without those repeated ACKs, the half-close recovery case completes after about two seconds. V3 stops the storm, but repeated ACKs can still prevent a half-closed connection from retrying. The earlier patch with the timer fix does retry under the same conditions. On Fri, Nov 20, 2026 at 9:18 PM Stefano Brivio wrote: > On Fri, 20 Nov 2026 23:07:56 +0530 > Anshu Kumari wrote: > > > Every duplicate ACK unconditionally triggered a fast retransmit, > > even when the ACK sequence hadn't advanced. > > > > Guard fast retransmit on !conn->retries, and increment retries > > after the first retransmit. This is a quick fix to stop the > > amplification storm. Full compliance with RFC 5681 Section 3.2 > > (three duplicate ACKs) is left to a later patch. > > Ada, would you have a chance to try this patch out? Would you like to > be credited with a Reported-by: tag? > > -- > Stefano > >