aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorEric Dumazet <[email protected]>2019-04-26 10:10:05 -0700
committerDavid S. Miller <[email protected]>2019-04-29 23:20:37 -0400
commitca2fe2956acef2f87f6c55549874fdd2e92d9824 (patch)
tree90154971d0ed9528cecb582a7c441577b9c243d7 /tools/perf/scripts/python/exported-sql-viewer.py
parent95c169251bf734aa555a1e8043e4d88ec97a04ec (diff)
tcp: add sanity tests in tcp_add_backlog()
Richard and Bruno both reported that my commit added a bug, and Bruno was able to determine the problem came when a segment wih a FIN packet was coalesced to a prior one in tcp backlog queue. It turns out the header prediction in tcp_rcv_established() looks back to TCP headers in the packet, not in the metadata (aka TCP_SKB_CB(skb)->tcp_flags) The fast path in tcp_rcv_established() is not supposed to handle a FIN flag (it does not call tcp_fin()) Therefore we need to make sure to propagate the FIN flag, so that the coalesced packet does not go through the fast path, the same than a GRO packet carrying a FIN flag. While we are at it, make sure we do not coalesce packets with RST or SYN, or if they do not have ACK set. Many thanks to Richard and Bruno for pinpointing the bad commit, and to Richard for providing a first version of the fix. Fixes: 4f693b55c3d2 ("tcp: implement coalescing on backlog queue") Signed-off-by: Eric Dumazet <[email protected]> Reported-by: Richard Purdie <[email protected]> Reported-by: Bruno PrĂ©mont <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions