tcp_cubic: fix the range of delayed_ack
authorLiu Yu <allanyuliu@tencent.com>
Wed, 30 Apr 2014 09:34:09 +0000 (17:34 +0800)
committerDavid S. Miller <davem@davemloft.net>
Wed, 30 Apr 2014 20:12:22 +0000 (16:12 -0400)
commit0cda345d1b2201dd15591b163e3c92bad5191745
tree9217f8842b799a02c7b2c531260c95b8029d9d27
parente5744fe9d262d11131916d04ea79ea539fe296c0
tcp_cubic: fix the range of delayed_ack

commit b9f47a3aaeab (tcp_cubic: limit delayed_ack ratio to prevent
divide error) try to prevent divide error, but there is still a little
chance that delayed_ack can reach zero. In case the param cnt get
negative value, then ratio+cnt would overflow and may happen to be zero.
As a result, min(ratio, ACK_RATIO_LIMIT) will calculate to be zero.

In some old kernels, such as 2.6.32, there is a bug that would
pass negative param, which then ultimately leads to this divide error.

commit 5b35e1e6e9c (tcp: fix tcp_trim_head() to adjust segment count
with skb MSS) fixed the negative param issue. However,
it's safe that we fix the range of delayed_ack as well,
to make sure we do not hit a divide by zero.

CC: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: Liu Yu <allanyuliu@tencent.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_cubic.c