diff options
| author | Eric Dumazet <edumazet@google.com> | 2015-04-09 13:31:56 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-04-09 17:28:57 -0400 |
| commit | b50edd7812852d989f2ef09dcfc729690f54a42d (patch) | |
| tree | 56a0bd0177ec020eb7381f4a20f4544d95b2f07f /net | |
| parent | b736a623bd099cdf5521ca9bd03559f3bc7fa31c (diff) | |
| download | linux-stable-b50edd7812852d989f2ef09dcfc729690f54a42d.tar.gz linux-stable-b50edd7812852d989f2ef09dcfc729690f54a42d.tar.bz2 linux-stable-b50edd7812852d989f2ef09dcfc729690f54a42d.zip | |
tcp: tcp_make_synack() should clear skb->tstamp
I noticed tcpdump was giving funky timestamps for locally
generated SYNACK messages on loopback interface.
11:42:46.938990 IP 127.0.0.1.48245 > 127.0.0.2.23850: S
945476042:945476042(0) win 43690 <mss 65495,nop,nop,sackOK,nop,wscale 7>
20:28:58.502209 IP 127.0.0.2.23850 > 127.0.0.1.48245: S
3160535375:3160535375(0) ack 945476043 win 43690 <mss
65495,nop,nop,sackOK,nop,wscale 7>
This is because we need to clear skb->tstamp before
entering lower stack, otherwise net_timestamp_check()
does not set skb->tstamp.
Fixes: 7faee5c0d514 ("tcp: remove TCP_SKB_CB(skb)->when")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
| -rw-r--r-- | net/ipv4/tcp_output.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c index 1db253e36045..d520492ba698 100644 --- a/net/ipv4/tcp_output.c +++ b/net/ipv4/tcp_output.c @@ -2929,6 +2929,8 @@ struct sk_buff *tcp_make_synack(struct sock *sk, struct dst_entry *dst, } #endif + /* Do not fool tcpdump (if any), clean our debris */ + skb->tstamp.tv64 = 0; return skb; } EXPORT_SYMBOL(tcp_make_synack); |