summaryrefslogtreecommitdiffstats
path: root/net/bridge/br_private_tunnel.h
diff options
context:
space:
mode:
authorIdo Schimmel <idosch@mellanox.com>2017-09-01 11:22:25 +0200
committerDavid S. Miller <davem@davemloft.net>2017-09-01 19:11:28 +0200
commit79e99bdd60b484af9afe0147e85a13e66d5c1cdb (patch)
tree9dd0f2cca668a57493ca09872ba8dae46c8df764 /net/bridge/br_private_tunnel.h
parentmlxsw: spectrum: Forbid linking to devices that have uppers (diff)
downloadlinux-79e99bdd60b484af9afe0147e85a13e66d5c1cdb.tar.xz
linux-79e99bdd60b484af9afe0147e85a13e66d5c1cdb.zip
bridge: switchdev: Clear forward mark when transmitting packet
Commit 6bc506b4fb06 ("bridge: switchdev: Add forward mark support for stacked devices") added the 'offload_fwd_mark' bit to the skb in order to allow drivers to indicate to the bridge driver that they already forwarded the packet in L2. In case the bit is set, before transmitting the packet from each port, the port's mark is compared with the mark stored in the skb's control block. If both marks are equal, we know the packet arrived from a switch device that already forwarded the packet and it's not re-transmitted. However, if the packet is transmitted from the bridge device itself (e.g., br0), we should clear the 'offload_fwd_mark' bit as the mark stored in the skb's control block isn't valid. This scenario can happen in rare cases where a packet was trapped during L3 forwarding and forwarded by the kernel to a bridge device. Fixes: 6bc506b4fb06 ("bridge: switchdev: Add forward mark support for stacked devices") Signed-off-by: Ido Schimmel <idosch@mellanox.com> Reported-by: Yotam Gigi <yotamg@mellanox.com> Tested-by: Yotam Gigi <yotamg@mellanox.com> Reviewed-by: Jiri Pirko <jiri@mellanox.com> Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge/br_private_tunnel.h')
0 files changed, 0 insertions, 0 deletions