From: Ido Schimmel <idosch@nvidia.com>
To: Wang Liang <wangliang74@huawei.com>
Cc: razor@blackwall.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
bridge@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yuehaibing@huawei.com,
zhangchangzhong@huawei.com
Subject: Re: [PATCH net v2] net: bridge: fix soft lockup in br_multicast_query_expired()
Date: Tue, 12 Aug 2025 09:10:47 +0300 [thread overview]
Message-ID: <aJra548HB7zGcA6K@shredder> (raw)
In-Reply-To: <20250812091818.542238-1-wangliang74@huawei.com>
On Tue, Aug 12, 2025 at 05:18:18PM +0800, Wang Liang wrote:
> When set multicast_query_interval to a large value, the local variable
> 'time' in br_multicast_send_query() may overflow. If the time is smaller
> than jiffies, the timer will expire immediately, and then call mod_timer()
> again, which creates a loop and may trigger the following soft lockup
> issue.
>
> watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66]
> CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none)
> Call Trace:
> <IRQ>
> __netdev_alloc_skb+0x2e/0x3a0
> br_ip6_multicast_alloc_query+0x212/0x1b70
> __br_multicast_send_query+0x376/0xac0
> br_multicast_send_query+0x299/0x510
> br_multicast_query_expired.constprop.0+0x16d/0x1b0
> call_timer_fn+0x3b/0x2a0
> __run_timers+0x619/0x950
> run_timer_softirq+0x11c/0x220
> handle_softirqs+0x18e/0x560
> __irq_exit_rcu+0x158/0x1a0
> sysvec_apic_timer_interrupt+0x76/0x90
> </IRQ>
>
> This issue can be reproduced with:
> ip link add br0 type bridge
> echo 1 > /sys/class/net/br0/bridge/multicast_querier
> echo 0xffffffffffffffff >
> /sys/class/net/br0/bridge/multicast_query_interval
> ip link set dev br0 up
>
> The multicast_startup_query_interval can also cause this issue. Similar to
> the commit 99b40610956a("net: bridge: mcast: add and enforce query interval
^ missing space
> minimum"), add check for the query interval maximum to fix this issue.
>
> Link: https://lore.kernel.org/netdev/20250806094941.1285944-1-wangliang74@huawei.com/
> Fixes: 7e4df51eb35d ("bridge: netlink: add support for igmp's intervals")
Probably doesn't matter in practice given how old both commits are, but
I think you should blame d902eee43f19 ("bridge: Add multicast
count/interval sysfs entries") instead. The commit message also uses the
sysfs path and not the netlink one.
> Suggested-by: Nikolay Aleksandrov <razor@blackwall.org>
> Signed-off-by: Wang Liang <wangliang74@huawei.com>
Code looks fine to me.
next prev parent reply other threads:[~2025-08-12 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:18 [PATCH net v2] net: bridge: fix soft lockup in br_multicast_query_expired() Wang Liang
2025-08-12 6:10 ` Ido Schimmel [this message]
2025-08-13 1:09 ` Wang Liang
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=aJra548HB7zGcA6K@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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).