Eric Dumazet 9669fffc14 net: ensure correct skb->tstamp in various fragmenters ... Thomas found that some forwarded packets would be stuck in FQ packet scheduler because their skb->tstamp contained timestamps far in the future. We thought we addressed this point in commit 8203e2d844 ("net: clear skb->tstamp in forwarding paths") but there is still an issue when/if a packet needs to be fragmented. In order to meet EDT requirements, we have to make sure all fragments get the original skb->tstamp. Note that this original skb->tstamp should be zero in forwarding path, but might have a non zero value in output path if user decided so. Fixes: fb420d5d91 ("tcp/fq: move back to CLOCK_MONOTONIC") Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: Thomas Bartschies <Thomas.Bartschies@cvk.de> Signed-off-by: David S. Miller <davem@davemloft.net>		2019-10-18 10:02:37 -07:00
..
ebt_802_3.c
ebt_among.c
ebt_arp.c
ebt_arpreply.c
ebt_dnat.c
ebt_ip.c
ebt_ip6.c
ebt_limit.c
ebt_log.c
ebt_mark.c
ebt_mark_m.c
ebt_nflog.c
ebt_pkttype.c
ebt_redirect.c
ebt_snat.c
ebt_stp.c
ebt_vlan.c
ebtable_broute.c
ebtable_filter.c
ebtable_nat.c
ebtables.c
Kconfig
Makefile
nf_conntrack_bridge.c	net: ensure correct skb->tstamp in various fragmenters	2019-10-18 10:02:37 -07:00
nf_log_bridge.c
nft_meta_bridge.c
nft_reject_bridge.c