tcp: ipv4: initialize unicast_sock sk_pacing_rate

When I added sk_pacing_rate field, I forgot to initialize its value
in the per cpu unicast_sock used in ip_send_unicast_reply()

This means that for sch_fq users, RST packets, or ACK packets sent
on behalf of TIME_WAIT sockets might be sent to slowly or even dropped
once we reach the per flow limit.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Fixes: 95bd09eb27 ("tcp: TSO packets automatic sizing")
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Eric Dumazet 2015-01-28 05:47:11 -08:00 committed by David S. Miller
parent 150ae0e946
commit 811230cd85

View File

@ -1517,6 +1517,7 @@ static DEFINE_PER_CPU(struct inet_sock, unicast_sock) = {
.sk_wmem_alloc = ATOMIC_INIT(1), .sk_wmem_alloc = ATOMIC_INIT(1),
.sk_allocation = GFP_ATOMIC, .sk_allocation = GFP_ATOMIC,
.sk_flags = (1UL << SOCK_USE_WRITE_QUEUE), .sk_flags = (1UL << SOCK_USE_WRITE_QUEUE),
.sk_pacing_rate = ~0U,
}, },
.pmtudisc = IP_PMTUDISC_WANT, .pmtudisc = IP_PMTUDISC_WANT,
.uc_ttl = -1, .uc_ttl = -1,