From: Vivien Didelot <hidden> Date: 2015-08-03 01:47:40
If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX,
an EDSA frame is prepended with a 802.1q header once queued.
To fix this, push the VLAN tag to the payload if present, before
checking the frame protocol.
[note: we may prefer to access directly VLAN TCI from hwaccel frames,
but this approach is simpler.]
Signed-off-by: Vivien Didelot <redacted>
---
net/dsa/tag_edsa.c | 5 +++++
1 file changed, 5 insertions(+)
From: David Miller <davem@davemloft.net> Date: 2015-08-04 05:22:02
From: Vivien Didelot <redacted>
Date: Sun, 2 Aug 2015 21:46:02 -0400
If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX,
an EDSA frame is prepended with a 802.1q header once queued.
To fix this, push the VLAN tag to the payload if present, before
checking the frame protocol.
[note: we may prefer to access directly VLAN TCI from hwaccel frames,
but this approach is simpler.]
Signed-off-by: Vivien Didelot <redacted>
This is a bug fix so should target 'net', but you generated the patch
against 'net-next'.
In any event, you should be explicit about the tree you are targetting
in order to not waste my time like this, by simply specifying the
tree in your "[PATCH xxx]" text in your subject line. Either
"[PATCH net]" or "[PATCH net-next]".
Thanks.
From: Vivien Didelot <hidden> Date: 2015-08-04 06:01:23
Hi David,
On Aug 4, 2015, at 1:21 AM, David davem@davemloft.net wrote:
From: Vivien Didelot <redacted>
Date: Sun, 2 Aug 2015 21:46:02 -0400
quoted
If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX,
an EDSA frame is prepended with a 802.1q header once queued.
To fix this, push the VLAN tag to the payload if present, before
checking the frame protocol.
[note: we may prefer to access directly VLAN TCI from hwaccel frames,
but this approach is simpler.]
Signed-off-by: Vivien Didelot <redacted>
This is a bug fix so should target 'net', but you generated the patch
against 'net-next'.
In any event, you should be explicit about the tree you are targetting
in order to not waste my time like this, by simply specifying the
tree in your "[PATCH xxx]" text in your subject line. Either
"[PATCH net]" or "[PATCH net-next]".