From: Nikolay Aleksandrov <razor@blackwall.org>
To: Cheng Yongkang <teel4res@gmail.com>, Ido Schimmel <idosch@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
bridge@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: bridge: mcast: release the EHT host budget for zero-address hosts
Date: Fri, 30 Oct 2026 10:22:35 +0200 [thread overview]
Message-ID: <788c84fa-12a4-4282-9afc-438d3206f21c@blackwall.org> (raw)
In-Reply-To: <179328314076.648427.17991367257682028617@gmail.com>
On 29/10/2026 16:12, Cheng Yongkang wrote:
> __eht_del_set_entry() decrements eht_host->num_entries only when the set
> entry's host address is non-zero. A report sent from the unspecified
> source address 0.0.0.0 (or in6addr_any for MLDv2) creates an EHT host
> with h_addr == 0, while the set entries created for its sources have
> non-zero source addresses and are counted against PG_SRC_ENT_LIMIT.
> Deleting those sources never releases the host's budget; after 32 counted
> sources the host stays at num_entries == 32 and every later counted set
> entry is refused. The same sequence with a non-zero report source
> releases the budget normally:
>
> host 0.0.0.0: IS_EXC/ALLOW1/BLOCK/ALLOW2 = 32/0/32/32
> host 10.9.9.9: IS_EXC/ALLOW1/BLOCK/ALLOW2 = 32/0/32/0
>
> Only set entries created for a non-zero source address are counted:
> br_multicast_create_eht_set_entry() rejects a zero source when
> allow_zero_src is false, and __eht_lookup_create_set_entry() increments
> num_entries only for those entries. The auto-created wildcard entry for
> a zero host uses allow_zero_src == true and is not counted. Release the
> budget based on eht_set->src_addr instead of h_addr, so counted entries
> decrement for zero-address hosts as well. The uncounted wildcard entry
> no longer decrements the counter, which also removes the converse
> mismatch for non-zero hosts.
>
> Fixes: baa74d39ca39 ("net: bridge: multicast: add EHT source set handling functions")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Cheng Yongkang <teel4res@gmail.com>
> ---
> net/bridge/br_multicast_eht.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/net/bridge/br_multicast_eht.c b/net/bridge/br_multicast_eht.c
> index 18eaf9c..548ad78 100644
> --- a/net/bridge/br_multicast_eht.c
> +++ b/net/bridge/br_multicast_eht.c
> @@ -167,7 +167,14 @@ static void __eht_del_set_entry(struct net_bridge_group_eht_set_entry *set_h)
> RB_CLEAR_NODE(&set_h->rb_node);
> hlist_del_init(&set_h->host_list);
> memset(&zero_addr, 0, sizeof(zero_addr));
> - if (memcmp(&set_h->h_addr, &zero_addr, sizeof(zero_addr)))
> + /* Only set entries created for a non-zero source address are counted
> + * towards the host's budget, the auto-created zero source entry is
> + * not (see __eht_lookup_create_set_entry()). Check the set's source
> + * address and not the host address: the host address can be zero as
> + * well (IGMPv3/MLDv2 allow an unspecified report source address), but
> + * its real source entries are still counted.
> + */
> + if (memcmp(&set_h->eht_set->src_addr, &zero_addr, sizeof(zero_addr)))
> eht_host->num_entries--;
> hlist_add_head(&set_h->mcast_gc.gc_node, &set_h->br->mcast_gc_list);
> queue_work(system_long_wq, &set_h->br->mcast_gc_work);
I don't think this is a -net fix, it can target net-next when it opens up.
You can also trim the comment, it is way too verbose for something so simple.
Thanks,
Nik
prev parent reply other threads:[~2026-10-30 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 14:12 [PATCH net] net: bridge: mcast: release the EHT host budget for zero-address hosts Cheng Yongkang
2026-10-29 14:18 ` netdev-bot+sinfo
2026-10-29 14:35 ` Cheng Yongkang
2026-10-30 8:22 ` 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=788c84fa-12a4-4282-9afc-438d3206f21c@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=teel4res@gmail.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