diff options
| author | Eric Dumazet <edumazet@google.com> | 2019-10-16 18:00:56 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-10 11:34:52 +0100 |
| commit | 95753984d8751580180ab0f06e6d3c2d0512da15 (patch) | |
| tree | 1a5cee8a25843d9672144431a511adeabda1f4e5 /lib/mpi/mpiutil.c | |
| parent | 96ed7673dcb92986956af16d877fb43dc98202c0 (diff) | |
net: ensure correct skb->tstamp in various fragmenters
[ Upstream commit 9669fffc1415bb0c30e5d2ec98a8e1c3a418cb9c ]
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 8203e2d844d3
("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: fb420d5d91c1 ("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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/mpi/mpiutil.c')
0 files changed, 0 insertions, 0 deletions