From: Toshiaki Makita Date: Wed, 16 Oct 2013 08:07:16 +0000 (+0900) Subject: bridge: Fix updating FDB entries when the PVID is applied X-Git-Tag: accepted/tizen/common/20141203.182822~1266^2~16^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=dfb5fa32c66496a53ec6a45302d902416b51ade2;p=platform%2Fkernel%2Flinux-arm64.git bridge: Fix updating FDB entries when the PVID is applied We currently set the value that variable vid is pointing, which will be used in FDB later, to 0 at br_allowed_ingress() when we receive untagged or priority-tagged frames, even though the PVID is valid. This leads to FDB updates in such a wrong way that they are learned with VID 0. Update the value to that of PVID if the PVID is applied. Signed-off-by: Toshiaki Makita Reviewed-by: Vlad Yasevich Signed-off-by: David S. Miller --- diff --git a/net/bridge/br_vlan.c b/net/bridge/br_vlan.c index 5a9c44a..53f0990 100644 --- a/net/bridge/br_vlan.c +++ b/net/bridge/br_vlan.c @@ -217,6 +217,7 @@ bool br_allowed_ingress(struct net_bridge *br, struct net_port_vlans *v, /* PVID is set on this port. Any untagged or priority-tagged * ingress frame is considered to belong to this vlan. */ + *vid = pvid; if (likely(err)) /* Untagged Frame. */ __vlan_hwaccel_put_tag(skb, htons(ETH_P_8021Q), pvid);