author | Eric Dumazet <edumazet@google.com> | |
Wed, 28 Jan 2015 13:47:11 +0000 (05:47 -0800) | ||
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
Fri, 27 Feb 2015 01:50:12 +0000 (17:50 -0800) | ||
commit | 2cec99c3e202a2704ada2ce040368f6efa333cd5 | |
tree | e3005c3b4c32d62d09738b6bb4c2ab900aef29f3 | tree | snapshot (tar.xz tar.gz zip) |
parent | 58a07b8e5a1eae96eef6e14d544a71698afc52b2 | commit | diff |
tcp: ipv4: initialize unicast_sock sk_pacing_rate
[ Upstream commit 811230cd853d62f09ed0addd0ce9a1b9b0e13fb5 ]
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[ Upstream commit 811230cd853d62f09ed0addd0ce9a1b9b0e13fb5 ]
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/ipv4/ip_output.c | diff | blob | history |