STRUCT NET_BRIDGE_VLAN_GROUP(9)

💅 struct net_bridge_vlan_group(9) — the Kernel API Manual, bestie edition 🎀

okay so this is a page from the Kernel API Manual and it's all about struct net_bridge_vlan_group — yes the NAME section is literally just the struct name and nothing else, she's mysterious like that ✨

🦋 SYNOPSIS 🦋

here's the whole struct, verbatim, no cap:

struct net_bridge_vlan_group {
    struct rhashtable               vlan_hash;
    struct rhashtable               tunnel_hash;
    struct list_head                vlan_list;
    u16 num_vlans;
    u16 pvid;
    u8 pvid_state;
 };

🌸 Members 🌸

• vlan_hash — the rhashtable holding your VLAN entries. it's giving "main character data structure" 💅
• tunnel_hash — hash table that maps from a tunnel key ID (like a VXLAN VNI, iykyk) to a VLAN 🌀
• vlan_list — a sorted list of VLAN entries. sorted! organized! iconic ✨
• num_vlans — the number of total VLAN entries, fr fr
• pvid — the PVID VLAN id 🏷️
• pvid_state — the PVID's STP state (like forwarding, learning, or blocking — pick your vibe) 🚦

💀 Description 💀

IMPORTANT: bestie please be careful when you're checking if there are VLAN entries using list primitives 😭 because the bridge can have entries in its list that are just for global context and not for filtering — meaning they have the master flag set but not the brentry flag. messy, I know.

so if you have to check whether there are "real" entries in the bridge, please please please test num_vlans instead 🙏 that's the whole assignment. that's the tea. 🍓

👑 SEE ALSO 👑

• Kernel file ./net/bridge/br_private.h
• struct net_bridge_vlan(9)

and that's the page! 🫶 brought to you by the good people in ./net/bridge, dated October 2026, with the footer reading struct net_b...e_vlan_group(9) — yes the title is abbreviated in the footer, she's shy 💖 slay, go forth and check your num_vlans 🌈⭐