From: Vlad Yasevich <vyasevic@redhat.com>
To: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>,
"David S . Miller" <davem@davemloft.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [PATCH net 1/2] bridge: Fix inabillity to retrieve vlan tags when tx offload is disabled
Date: Thu, 27 Mar 2014 17:33:32 -0400 [thread overview]
Message-ID: <5334992C.20903@redhat.com> (raw)
In-Reply-To: <1395924416-12325-1-git-send-email-makita.toshiaki@lab.ntt.co.jp>
On 03/27/2014 08:46 AM, Toshiaki Makita wrote:
> Bridge vlan code (br_vlan_get_tag()) assumes that all frames have vlan_tci
> if they are tagged, but if vlan tx offload is manually disabled on bridge
> device and frames are sent from vlan device on the bridge device, the tags
> are embedded in skb->data and they break this assumption.
> Extract embedded vlan tags and move them to vlan_tci at ingress.
>
> Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Acked-by: Vlad Yasevich <vyasevic@redhat.com>
-vlad
> ---
> net/bridge/br_device.c | 6 +++---
> net/bridge/br_vlan.c | 12 ++++++++++++
> 2 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/net/bridge/br_device.c b/net/bridge/br_device.c
> index 63f0455..8fe8b71 100644
> --- a/net/bridge/br_device.c
> +++ b/net/bridge/br_device.c
> @@ -49,14 +49,14 @@ netdev_tx_t br_dev_xmit(struct sk_buff *skb, struct net_device *dev)
> brstats->tx_bytes += skb->len;
> u64_stats_update_end(&brstats->syncp);
>
> - if (!br_allowed_ingress(br, br_get_vlan_info(br), skb, &vid))
> - goto out;
> -
> BR_INPUT_SKB_CB(skb)->brdev = dev;
>
> skb_reset_mac_header(skb);
> skb_pull(skb, ETH_HLEN);
>
> + if (!br_allowed_ingress(br, br_get_vlan_info(br), skb, &vid))
> + goto out;
> +
> if (is_broadcast_ether_addr(dest))
> br_flood_deliver(br, skb, false);
> else if (is_multicast_ether_addr(dest)) {
> diff --git a/net/bridge/br_vlan.c b/net/bridge/br_vlan.c
> index 8249ca7..44f31af 100644
> --- a/net/bridge/br_vlan.c
> +++ b/net/bridge/br_vlan.c
> @@ -174,6 +174,18 @@ bool br_allowed_ingress(struct net_bridge *br, struct net_port_vlans *v,
> if (!v)
> return false;
>
> + /* If vlan tx offload is disabled on bridge device and frame was
> + * sent from vlan device on the bridge device, it does not have
> + * HW accelerated vlan tag.
> + */
> + if (unlikely(!vlan_tx_tag_present(skb) &&
> + (skb->protocol == htons(ETH_P_8021Q) ||
> + skb->protocol == htons(ETH_P_8021AD)))) {
> + skb = vlan_untag(skb);
> + if (unlikely(!skb))
> + return false;
> + }
> +
> err = br_vlan_get_tag(skb, vid);
> if (!*vid) {
> u16 pvid = br_get_pvid(v);
>
next prev parent reply other threads:[~2014-03-27 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:46 [PATCH net 1/2] bridge: Fix inabillity to retrieve vlan tags when tx offload is disabled Toshiaki Makita
2014-03-27 12:46 ` [PATCH net 2/2] bridge: Fix handling stacked vlan tags Toshiaki Makita
2014-03-27 21:35 ` Vlad Yasevich
2014-03-28 20:33 ` David Miller
2014-03-27 21:33 ` Vlad Yasevich [this message]
2014-03-28 20:33 ` [PATCH net 1/2] bridge: Fix inabillity to retrieve vlan tags when tx offload is disabled David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5334992C.20903@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).