From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: Vlad Yasevich <vyasevic@redhat.com>,
shemminger@vyatta.com, bridge@lists.linux-foundation.org
Subject: [PATCH v3 net 0/2] bridge: Fix forwarding of 8021AD frames
Date: Thu, 27 Mar 2014 17:32:28 -0400 [thread overview]
Message-ID: <1395955950-17630-1-git-send-email-vyasevic@redhat.com> (raw)
Bridge has its own way to deterine if the packet is forwardable and it doesn't
support 8021ad tags correctly. Instead just allow bridge to use an
existing is_skb_forwardable() function.
v2: Fix missing hunk in patch 2/2 to make it build.
v3: Fix indent for is_skb_forwardable
Vlad Yasevich (2):
net: Allow modules to use is_skb_forwardable
bridge: use is_skb_forwardable in forward path
include/linux/netdevice.h | 1 +
net/bridge/br_forward.c | 9 ++-------
net/core/dev.c | 3 ++-
3 files changed, 5 insertions(+), 8 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-03-27 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 21:32 Vlad Yasevich [this message]
2014-03-27 21:32 ` [PATCH v3 net 1/2] net: Allow modules to use is_skb_forwardable Vlad Yasevich
2014-03-27 21:32 ` [PATCH v3 net 2/2] bridge: use is_skb_forwardable in forward path Vlad Yasevich
2014-03-31 20:04 ` [PATCH v3 net 0/2] bridge: Fix forwarding of 8021AD frames 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=1395955950-17630-1-git-send-email-vyasevic@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).