From: Priyaranjan Jha <priyarjha.ker...@gmail.com> Date: Thu, 24 Sep 2020 15:23:14 -0700
> From: Priyaranjan Jha <priyar...@google.com> > > Currently, we use length of DSACKed range to compute number of > delivered packets. And if sequence range in DSACK is corrupted, > we can get bogus dsacked/acked count, and bogus cwnd. > > This patch put bounds on DSACKed range to skip update of data > delivery and spurious retransmission information, if the DSACK > is unlikely caused by sender's action: > - DSACKed range shouldn't be greater than maximum advertised rwnd. > - Total no. of DSACKed segments shouldn't be greater than total > no. of retransmitted segs. Unlike spurious retransmits, network > duplicates or corrupted DSACKs shouldn't be counted as delivery. > > Signed-off-by: Priyaranjan Jha <priyar...@google.com> > Signed-off-by: Neal Cardwell <ncardw...@google.com> > Signed-off-by: Yuchung Cheng <ych...@google.com> > Signed-off-by: Eric Dumazet <eduma...@google.com> Applied and queued up for -stable, thanks.
