Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Luke Howard <lukeh@padl.com>, Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Ido Schimmel <idosch@nvidia.com>, Simon Horman <horms@kernel.org>
Cc: Cedric Jehasse <cedric.jehasse@gmail.com>,
	Kieran Tyrrell <kieran@sienda.com>,
	Max Holtmann <mh@rme-audio.de>, Max Hunter <max@huntershome.org>,
	Christoph Mellauner <christoph.mellauner@joyned.at>,
	Simon Gapp <simon.gapp@gapp-audio.com>,
	netdev@vger.kernel.org, bridge@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC net-next] net: bridge: add BRIDGE_VLAN_INFO_DYNAMIC flag
Date: Fri, 3 Jul 2026 10:34:18 +0300	[thread overview]
Message-ID: <45fa2de3-1b56-48b3-a946-ae4c7ea26a22@blackwall.org> (raw)
In-Reply-To: <20260703-vlan-dynamic-entry-v1-1-c2cbb134036c@padl.com>

On 03/07/2026 09:54, Luke Howard wrote:
> Dynamic VLAN entries as specified in IEEE Std 802.1Q-2022,
> Clause 8.8.5. These allow a user-space VLAN registration
> protocol such as MVRP to mark a bridge's VLAN entries as
> dynamic, so they can be distinguished from administratively
> configured static entries.
> 
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Luke Howard <lukeh@padl.com>
> ---
> This patch adds support for Dynamic VLAN Entries, as specified
> in 802.1Q. I have marked it as RFC as a similar patch to add
> support for Dynamic Reservation Entries to the FDB was rejected
> on the argument that the dynamic bit should be stored separately.
> 
> Our MVRP implementation [1] will use this flag if available.
> 
> [1] https://github.com/PADL/OpenSRP

Hi,
Do this tracking entirely in your app, it doesn't bring anything to the
kernel and just adding flags because it is convenient is not acceptable.
These VLANs are the same from kernel POV and this flag doesn't change
anything functionally.
Alternatively perhaps a proto field similar to routes could help you out to
distinguish who installed a VLAN entry, not sure if that would help your
user-space app though, and you'll have to add a new rt proto id that should
get accepted.

Cheers,
  Nik

> ---
>   include/uapi/linux/if_bridge.h |  1 +
>   net/bridge/br_netlink.c        |  6 ++++++
>   net/bridge/br_vlan.c           | 18 ++++++++++++++----
>   3 files changed, 21 insertions(+), 4 deletions(-)
> 
> diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h
> index 21a700c02ef76..a3abbfe79694b 100644
> --- a/include/uapi/linux/if_bridge.h
> +++ b/include/uapi/linux/if_bridge.h
> @@ -134,6 +134,7 @@ enum {
>   #define BRIDGE_VLAN_INFO_RANGE_END	(1<<4) /* VLAN is end of vlan range */
>   #define BRIDGE_VLAN_INFO_BRENTRY	(1<<5) /* Global bridge VLAN entry */
>   #define BRIDGE_VLAN_INFO_ONLY_OPTS	(1<<6) /* Skip create/delete/flags */
> +#define BRIDGE_VLAN_INFO_DYNAMIC	(1<<7) /* 802.1Q Dynamic VLAN Registration Entry */
>   
>   struct bridge_vlan_info {
>   	__u16 flags;
> diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c
> index b2cd4e39326d0..90f2e103f53d5 100644
> --- a/net/bridge/br_netlink.c
> +++ b/net/bridge/br_netlink.c
> @@ -388,6 +388,9 @@ static int br_fill_ifvlaninfo_compressed(struct sk_buff *skb,
>   		if (v->flags & BRIDGE_VLAN_INFO_UNTAGGED)
>   			flags |= BRIDGE_VLAN_INFO_UNTAGGED;
>   
> +		if (v->flags & BRIDGE_VLAN_INFO_DYNAMIC)
> +			flags |= BRIDGE_VLAN_INFO_DYNAMIC;
> +
>   		if (vid_range_start == 0) {
>   			goto initvars;
>   		} else if ((v->vid - vid_range_end) == 1 &&
> @@ -440,6 +443,9 @@ static int br_fill_ifvlaninfo(struct sk_buff *skb,
>   		if (v->flags & BRIDGE_VLAN_INFO_UNTAGGED)
>   			vinfo.flags |= BRIDGE_VLAN_INFO_UNTAGGED;
>   
> +		if (v->flags & BRIDGE_VLAN_INFO_DYNAMIC)
> +			vinfo.flags |= BRIDGE_VLAN_INFO_DYNAMIC;
> +
>   		if (nla_put(skb, IFLA_BRIDGE_VLAN_INFO,
>   			    sizeof(vinfo), &vinfo))
>   			goto nla_put_failure;
> diff --git a/net/bridge/br_vlan.c b/net/bridge/br_vlan.c
> index 5560afcaaca32..e6bc59e3a4c4f 100644
> --- a/net/bridge/br_vlan.c
> +++ b/net/bridge/br_vlan.c
> @@ -54,9 +54,11 @@ static void __vlan_delete_pvid(struct net_bridge_vlan_group *vg, u16 vid)
>   	vg->pvid = 0;
>   }
>   
> -/* Update the BRIDGE_VLAN_INFO_PVID and BRIDGE_VLAN_INFO_UNTAGGED flags of @v.
> - * If @commit is false, return just whether the BRIDGE_VLAN_INFO_PVID and
> - * BRIDGE_VLAN_INFO_UNTAGGED bits of @flags would produce any change onto @v.
> +/* Update the BRIDGE_VLAN_INFO_PVID, BRIDGE_VLAN_INFO_UNTAGGED and
> + * BRIDGE_VLAN_INFO_DYNAMIC flags of @v.
> + * If @commit is false, return just whether the BRIDGE_VLAN_INFO_PVID,
> + * BRIDGE_VLAN_INFO_UNTAGGED and BRIDGE_VLAN_INFO_DYNAMIC bits of @flags
> + * would produce any change onto @v.
>    */
>   static bool __vlan_flags_update(struct net_bridge_vlan *v, u16 flags,
>   				bool commit)
> @@ -71,7 +73,8 @@ static bool __vlan_flags_update(struct net_bridge_vlan *v, u16 flags,
>   
>   	/* check if anything would be changed on commit */
>   	change = !!(flags & BRIDGE_VLAN_INFO_PVID) == !!(vg->pvid != v->vid) ||
> -		 ((flags ^ v->flags) & BRIDGE_VLAN_INFO_UNTAGGED);
> +		 ((flags ^ v->flags) & (BRIDGE_VLAN_INFO_UNTAGGED |
> +					BRIDGE_VLAN_INFO_DYNAMIC));
>   
>   	if (!commit)
>   		goto out;
> @@ -86,6 +89,11 @@ static bool __vlan_flags_update(struct net_bridge_vlan *v, u16 flags,
>   	else
>   		v->flags &= ~BRIDGE_VLAN_INFO_UNTAGGED;
>   
> +	if (flags & BRIDGE_VLAN_INFO_DYNAMIC)
> +		v->flags |= BRIDGE_VLAN_INFO_DYNAMIC;
> +	else
> +		v->flags &= ~BRIDGE_VLAN_INFO_DYNAMIC;
> +
>   out:
>   	return change;
>   }
> @@ -1874,6 +1882,8 @@ static bool br_vlan_fill_vids(struct sk_buff *skb, u16 vid, u16 vid_range,
>   		info.flags |= BRIDGE_VLAN_INFO_UNTAGGED;
>   	if (flags & BRIDGE_VLAN_INFO_PVID)
>   		info.flags |= BRIDGE_VLAN_INFO_PVID;
> +	if (flags & BRIDGE_VLAN_INFO_DYNAMIC)
> +		info.flags |= BRIDGE_VLAN_INFO_DYNAMIC;
>   
>   	if (nla_put(skb, BRIDGE_VLANDB_ENTRY_INFO, sizeof(info), &info))
>   		goto out_err;
> 
> ---
> base-commit: 2bb62a85aff6d4c14a62a476dfabaada3c1cc014
> change-id: 20260703-vlan-dynamic-entry-56a028e8990e
> 
> Best regards,
> --
> Luke Howard <lukeh@padl.com>
> 


      reply	other threads:[~2026-07-03  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  6:54 [PATCH RFC net-next] net: bridge: add BRIDGE_VLAN_INFO_DYNAMIC flag Luke Howard
2026-07-03  7:34 ` Nikolay Aleksandrov [this message]

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=45fa2de3-1b56-48b3-a946-ae4c7ea26a22@blackwall.org \
    --to=razor@blackwall.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bridge@lists.linux.dev \
    --cc=cedric.jehasse@gmail.com \
    --cc=christoph.mellauner@joyned.at \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kieran@sienda.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukeh@padl.com \
    --cc=max@huntershome.org \
    --cc=mh@rme-audio.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.gapp@gapp-audio.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