From: Mike Manning <mmanning@vyatta.att-mail.com>
To: netdev@vger.kernel.org, nikolay@cumulusnetworks.com,
roopa@cumulusnetworks.com
Subject: [PATCH net-next v2 0/5] net: support binding vlan dev link state to vlan member bridge ports
Date: Wed, 17 Apr 2019 19:16:24 +0100 [thread overview]
Message-ID: <20190417181629.5791-1-mmanning@vyatta.att-mail.com> (raw)
For vlan filtering on bridges, the bridge may also have vlan devices
as upper devices. For switches, these are used to provide L3 packet
processing for ports that are members of a given vlan.
While it is correct that the admin state for these vlan devices is
either set directly for the device or inherited from the lower device,
the link state is also transferred from the lower device. So this is
always up if the bridge is in admin up state and there is at least one
bridge port that is up, regardless of the vlan that the port is in.
The link state of the vlan device may need to track only the state of
the subset of ports that are also members of the corresponding vlan,
rather than that of all ports.
This series provides an optional vlan flag so that the link state of
the vlan device is only up if there is at least one bridge port that is
up AND is a member of the corresponding vlan.
Mike Manning (5):
vlan: support binding link state to vlan member bridge ports
vlan: do not transfer link state in vlan bridge binding mode
bridge: support binding vlan dev link state to vlan member bridge
ports
bridge: update vlan dev state when port added to or deleted from vlan
bridge: update vlan dev link state for bridge netdev changes
include/uapi/linux/if_vlan.h | 9 +-
net/8021q/vlan.c | 18 +++-
net/8021q/vlan_dev.c | 22 +++--
net/8021q/vlan_netlink.c | 3 +-
net/bridge/br.c | 17 +++-
net/bridge/br_private.h | 14 +++
net/bridge/br_vlan.c | 214 +++++++++++++++++++++++++++++++++++++++++++
7 files changed, 276 insertions(+), 21 deletions(-)
--
2.11.0
next reply other threads:[~2019-04-17 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 18:16 Mike Manning [this message]
2019-04-17 18:16 ` [PATCH net-next v2 1/5] vlan: support binding link state to vlan member bridge ports Mike Manning
2019-04-18 11:25 ` Nikolay Aleksandrov
2019-04-17 18:16 ` [PATCH net-next v2 2/5] vlan: do not transfer link state in vlan bridge binding mode Mike Manning
2019-04-18 11:25 ` Nikolay Aleksandrov
2019-04-17 18:16 ` [PATCH net-next v2 3/5] bridge: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-18 11:28 ` Nikolay Aleksandrov
2019-04-18 14:42 ` Mike Manning
2019-04-17 18:16 ` [PATCH net-next v2 4/5] bridge: update vlan dev state when port added to or deleted from vlan Mike Manning
2019-04-18 11:41 ` Nikolay Aleksandrov
2019-04-17 18:16 ` [PATCH net-next v2 5/5] bridge: update vlan dev link state for bridge netdev changes Mike Manning
2019-04-18 11:45 ` Nikolay Aleksandrov
2019-04-18 11:43 ` [PATCH net-next v2 0/5] net: support binding vlan dev link state to vlan member bridge ports Nikolay Aleksandrov
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=20190417181629.5791-1-mmanning@vyatta.att-mail.com \
--to=mmanning@vyatta.att-mail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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).