tcp: ipv4: initialize unicast_sock sk_pacing_rate
authorEric Dumazet <edumazet@google.com>
Wed, 28 Jan 2015 13:47:11 +0000 (05:47 -0800)
committerDavid S. Miller <davem@davemloft.net>
Thu, 29 Jan 2015 07:24:47 +0000 (23:24 -0800)
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: 95bd09eb2750 ("tcp: TSO packets automatic sizing")
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/ip_output.c

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