Skip to content
Snippets Groups Projects
Select Git revision
  • 0ce294d88457bccd7f9991f883fec80022a1ddbd
  • master default
  • android-container
  • nanopc-t4
  • for-kernelci
  • WIP-syscall
  • v4.16-rc5
  • v4.16-rc4
  • v4.16-rc3
  • v4.16-rc2
  • v4.16-rc1
  • v4.15
  • v4.15-rc9
  • v4.15-rc8
  • v4.15-rc7
  • v4.15-rc6
  • v4.15-rc5
  • v4.15-rc4
  • v4.15-rc3
  • v4.15-rc2
  • v4.15-rc1
  • v4.14
  • v4.14-rc8
  • v4.14-rc7
  • v4.14-rc6
  • v4.14-rc5
26 results

linux

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Yuchung Cheng authored and David S. Miller committed
    RACK does not test the loss recovery state correctly to compute
    the reordering window. It assumes if lost_out is zero then TCP is
    not in loss recovery. But it can be zero during recovery before
    calling tcp_rack_detect_loss(): when an ACK acknowledges all
    packets marked lost before receiving this ACK, but has not yet
    to discover new ones by tcp_rack_detect_loss(). The fix is to
    simply test the congestion state directly.
    
    Signed-off-by: default avatarYuchung Cheng <ycheng@google.com>
    Reviewed-by: default avatarNeal Cardwell <ncardwell@google.com>
    Reviewed-by: default avatarPriyaranjan Jha <priyarjha@google.com>
    Reviewed-by: default avatarEric Dumazet <edumazet@google.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    0ce294d8
    History
    Name Last commit Last update