From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Mike Manning <mmanning@vyatta.att-mail.com>,
netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 1/5] vlan: support binding link state to vlan member bridge ports
Date: Thu, 18 Apr 2019 14:25:00 +0300 [thread overview]
Message-ID: <b1721cc8-04aa-e8bf-dd70-cdd8d6f780bb@cumulusnetworks.com> (raw)
In-Reply-To: <20190417181629.5791-2-mmanning@vyatta.att-mail.com>
On 17/04/2019 21:16, Mike Manning wrote:
> In the case of vlan filtering on bridges, the bridge may also have the
> corresponding vlan devices as upper devices. Currently the link state
> of vlan devices is transferred from the lower device. So this is 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 a member of.
>
> 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.
>
> Add a flag to specify a vlan bridge binding mode, by which the link
> state is no longer automatically transferred from the lower device,
> but is instead determined by the bridge ports that are members of the
> vlan.
>
> Signed-off-by: Mike Manning <mmanning@vyatta.att-mail.com>
> ---
> include/uapi/linux/if_vlan.h | 9 +++++----
> net/8021q/vlan_dev.c | 3 ++-
> net/8021q/vlan_netlink.c | 3 ++-
> 3 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/include/uapi/linux/if_vlan.h b/include/uapi/linux/if_vlan.h
> index 7a0e8bd65b6b..90a2c89afc8f 100644
> --- a/include/uapi/linux/if_vlan.h
> +++ b/include/uapi/linux/if_vlan.h
> @@ -32,10 +32,11 @@ enum vlan_ioctl_cmds {
> };
>
> enum vlan_flags {
> - VLAN_FLAG_REORDER_HDR = 0x1,
> - VLAN_FLAG_GVRP = 0x2,
> - VLAN_FLAG_LOOSE_BINDING = 0x4,
> - VLAN_FLAG_MVRP = 0x8,
> + VLAN_FLAG_REORDER_HDR = 0x1,
> + VLAN_FLAG_GVRP = 0x2,
> + VLAN_FLAG_LOOSE_BINDING = 0x4,
> + VLAN_FLAG_MVRP = 0x8,
> + VLAN_FLAG_BRIDGE_BINDING = 0x10,
> };
>
> enum vlan_name_types {
> diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
> index 8d77b6ee4477..ed996b500b10 100644
> --- a/net/8021q/vlan_dev.c
> +++ b/net/8021q/vlan_dev.c
> @@ -223,7 +223,8 @@ int vlan_dev_change_flags(const struct net_device *dev, u32 flags, u32 mask)
> u32 old_flags = vlan->flags;
>
> if (mask & ~(VLAN_FLAG_REORDER_HDR | VLAN_FLAG_GVRP |
> - VLAN_FLAG_LOOSE_BINDING | VLAN_FLAG_MVRP))
> + VLAN_FLAG_LOOSE_BINDING | VLAN_FLAG_MVRP |
> + VLAN_FLAG_BRIDGE_BINDING))
> return -EINVAL;
>
> vlan->flags = (old_flags & ~mask) | (flags & mask);
> diff --git a/net/8021q/vlan_netlink.c b/net/8021q/vlan_netlink.c
> index 9b60c1e399e2..a624dccf68fd 100644
> --- a/net/8021q/vlan_netlink.c
> +++ b/net/8021q/vlan_netlink.c
> @@ -84,7 +84,8 @@ static int vlan_validate(struct nlattr *tb[], struct nlattr *data[],
> flags = nla_data(data[IFLA_VLAN_FLAGS]);
> if ((flags->flags & flags->mask) &
> ~(VLAN_FLAG_REORDER_HDR | VLAN_FLAG_GVRP |
> - VLAN_FLAG_LOOSE_BINDING | VLAN_FLAG_MVRP)) {
> + VLAN_FLAG_LOOSE_BINDING | VLAN_FLAG_MVRP |
> + VLAN_FLAG_BRIDGE_BINDING)) {
> NL_SET_ERR_MSG_MOD(extack, "Invalid VLAN flags");
> return -EINVAL;
> }
>
Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
next prev parent reply other threads:[~2019-04-18 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 18:16 [PATCH net-next v2 0/5] net: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-17 18:16 ` [PATCH net-next v2 1/5] vlan: support binding " Mike Manning
2019-04-18 11:25 ` Nikolay Aleksandrov [this message]
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=b1721cc8-04aa-e8bf-dd70-cdd8d6f780bb@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=mmanning@vyatta.att-mail.com \
--cc=netdev@vger.kernel.org \
--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).