From: Paolo Abeni
Date: Tue, 8 Jan 2019 18:45:05 +0100
> Matteo reported forwarding issues inside the linux bridge,
> if the enslaved interfaces use the fq qdisc.
>
> Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in
> forwarding paths"), we need to clear the tstamp field in
> the brid
On 01/08/2019 09:45 AM, Paolo Abeni wrote:
> Matteo reported forwarding issues inside the linux bridge,
> if the enslaved interfaces use the fq qdisc.
>
> Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in
> forwarding paths"), we need to clear the tstamp field in
> the bridge forwardin
On Tue, Jan 8, 2019 at 9:45 AM Paolo Abeni wrote:
>
> Matteo reported forwarding issues inside the linux bridge,
> if the enslaved interfaces use the fq qdisc.
>
> Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in
> forwarding paths"), we need to clear the tstamp field in
> the bridge for
On 08/01/2019 19:45, Paolo Abeni wrote:
> Matteo reported forwarding issues inside the linux bridge,
> if the enslaved interfaces use the fq qdisc.
>
> Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in
> forwarding paths"), we need to clear the tstamp field in
> the bridge forwarding path
Matteo reported forwarding issues inside the linux bridge,
if the enslaved interfaces use the fq qdisc.
Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in
forwarding paths"), we need to clear the tstamp field in
the bridge forwarding path.
Fixes: 80b14dee2bea ("net: Add a new socket optio
