From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: idosch@nvidia.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
bridge@lists.linux.dev, Nikolay Aleksandrov <razor@blackwall.org>
Subject: [PATCH net-next 2/9] net: bridge: factor out port flooding
Date: Fri, 18 Sep 2026 18:29:43 +0300 [thread overview]
Message-ID: <20260918152950.1938259-3-razor@blackwall.org> (raw)
In-Reply-To: <20260918152950.1938259-1-razor@blackwall.org>
Factor out port flooding code into its own helper, it will be used by later
changes to flood to specific port VLANs. No functional changes intended.
Signed-off-by: Nikolay Aleksandrov <razor@blackwall.org>
---
net/bridge/br_forward.c | 77 +++++++++++++++++++++++------------------
1 file changed, 43 insertions(+), 34 deletions(-)
diff --git a/net/bridge/br_forward.c b/net/bridge/br_forward.c
index 31d54125b441..a696c6c128e3 100644
--- a/net/bridge/br_forward.c
+++ b/net/bridge/br_forward.c
@@ -219,6 +219,48 @@ static void br_flood_finish(struct net_bridge_port *prev, struct sk_buff *skb,
__br_forward(prev, skb, local_orig);
}
+static void br_flood_port(struct net_bridge_port **prev,
+ struct net_bridge_port *p, struct sk_buff *skb,
+ enum br_pkt_type pkt_type, bool local_orig, u16 vid)
+{
+ /* Do not flood unicast traffic to ports that turn it off, nor
+ * other traffic if flood off, except for traffic we originate
+ */
+ switch (pkt_type) {
+ case BR_PKT_UNICAST:
+ if (!test_bit(BR_FLOOD_BIT, &p->flags))
+ return;
+ break;
+ case BR_PKT_MULTICAST:
+ if (!test_bit(BR_MCAST_FLOOD_BIT, &p->flags) &&
+ skb->dev != p->br->dev)
+ return;
+ break;
+ case BR_PKT_BROADCAST:
+ if (!test_bit(BR_BCAST_FLOOD_BIT, &p->flags) &&
+ skb->dev != p->br->dev)
+ return;
+ break;
+ }
+
+ /* Do not flood to ports that enable proxy ARP */
+ if (test_bit(BR_PROXYARP_BIT, &p->flags))
+ return;
+ if (BR_INPUT_SKB_CB(skb)->proxyarp_replied) {
+ if (test_bit(BR_PROXYARP_WIFI_BIT, &p->flags))
+ return;
+ /* For gratuitous ARPs/NAs, check neigh_forward_grat.
+ * For regular ARPs/NDs, check only neigh_suppress.
+ */
+ if (br_is_neigh_suppress_enabled(p, vid) &&
+ (!BR_INPUT_SKB_CB(skb)->grat_arp ||
+ !br_is_neigh_forward_grat_enabled(p, vid)))
+ return;
+ }
+
+ *prev = maybe_deliver(*prev, p, skb, local_orig);
+}
+
/* called under rcu_read_lock */
void br_flood(struct net_bridge *br, struct sk_buff *skb,
enum br_pkt_type pkt_type, bool local_rcv, bool local_orig,
@@ -230,40 +272,7 @@ void br_flood(struct net_bridge *br, struct sk_buff *skb,
br_tc_skb_miss_set(skb, pkt_type != BR_PKT_BROADCAST);
list_for_each_entry_rcu(p, &br->port_list, list) {
- /* Do not flood unicast traffic to ports that turn it off, nor
- * other traffic if flood off, except for traffic we originate
- */
- switch (pkt_type) {
- case BR_PKT_UNICAST:
- if (!test_bit(BR_FLOOD_BIT, &p->flags))
- continue;
- break;
- case BR_PKT_MULTICAST:
- if (!test_bit(BR_MCAST_FLOOD_BIT, &p->flags) && skb->dev != br->dev)
- continue;
- break;
- case BR_PKT_BROADCAST:
- if (!test_bit(BR_BCAST_FLOOD_BIT, &p->flags) && skb->dev != br->dev)
- continue;
- break;
- }
-
- /* Do not flood to ports that enable proxy ARP */
- if (test_bit(BR_PROXYARP_BIT, &p->flags))
- continue;
- if (BR_INPUT_SKB_CB(skb)->proxyarp_replied) {
- if (test_bit(BR_PROXYARP_WIFI_BIT, &p->flags))
- continue;
- /* For gratuitous ARPs/NAs, check neigh_forward_grat.
- * For regular ARPs/NDs, check only neigh_suppress.
- */
- if (br_is_neigh_suppress_enabled(p, vid) &&
- (!BR_INPUT_SKB_CB(skb)->grat_arp ||
- !br_is_neigh_forward_grat_enabled(p, vid)))
- continue;
- }
-
- prev = maybe_deliver(prev, p, skb, local_orig);
+ br_flood_port(&prev, p, skb, pkt_type, local_orig, vid);
if (IS_ERR(prev))
break;
}
--
2.47.3
next prev parent reply other threads:[~2026-09-18 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 15:29 [PATCH net-next 0/9] net: bridge: vlan: broadcast fwding path optimizations Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 1/9] net: bridge: factor out common flood completion handling Nikolay Aleksandrov
2026-09-18 15:29 ` Nikolay Aleksandrov [this message]
2026-09-18 15:29 ` [PATCH net-next 3/9] net: bridge: vlan: cache the pvid vlan entry directly Nikolay Aleksandrov
2026-09-19 18:07 ` Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 4/9] net: bridge: vlan: introduce a list of port-VLANs in the master VLAN Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 5/9] net: bridge: consider only port-VLAN members when flooding Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 6/9] net: bridge: vlan: use an RCU array for large flood sets Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 7/9] net: bridge: introduce a forwarding destination structure Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 8/9] net: bridge: avoid egress VLAN lookups when flooding Nikolay Aleksandrov
2026-09-18 15:29 ` [PATCH net-next 9/9] net: bridge: avoid VLAN lookups for flood neighbour suppression Nikolay Aleksandrov
2026-09-21 13:44 ` [PATCH net-next 0/9] net: bridge: vlan: broadcast fwding path optimizations Ido Schimmel
2026-09-21 13:57 ` Nikolay Aleksandrov
2026-09-22 0:50 ` patchwork-bot+netdevbpf
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=20260918152950.1938259-3-razor@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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