Skip to content

Conversation

wedsonaf
Copy link

This is just a rename followed by rustfmt, no functional change is
intended.

Signed-off-by: Wedson Almeida Filho wedsonaf@google.com

@wedsonaf
Copy link
Author

@ojeda this looks to be related to the CI. Is there anything I can do to make this go away?

E: The repository 'https://packages.microsoft.com/repos/azure-cli focal Release' no longer has a Release file.

@ojeda
Copy link
Member

ojeda commented May 10, 2021

It happens from time to time :(

We will just wait a few hours, I guess.

This is just a rename followed by `rustfmt`, no functional change is
intended.

Signed-off-by: Wedson Almeida Filho <wedsonaf@google.com>
@TheSven73
Copy link
Collaborator

I did a quick read through, and LGTM.

@alex
Copy link
Member

alex commented May 11, 2021

This is going to cause merge conflicts everywhere. Sorry :-(

@alex alex merged commit 56e7e87 into Rust-for-Linux:rust May 11, 2021
@wedsonaf wedsonaf deleted the result branch May 11, 2021 18:52
ojeda pushed a commit that referenced this pull request Aug 25, 2025
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 99b4061 ("net: bridge: mcast: add and enforce query
interval minimum"), add check for the query interval maximum to fix this
issue.

Link: https://lore.kernel.org/netdev/20250806094941.1285944-1-wangliang74@huawei.com/
Link: https://lore.kernel.org/netdev/20250812091818.542238-1-wangliang74@huawei.com/
Fixes: d902eee ("bridge: Add multicast count/interval sysfs entries")
Suggested-by: Nikolay Aleksandrov <razor@blackwall.org>
Signed-off-by: Wang Liang <wangliang74@huawei.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
Link: https://patch.msgid.link/20250813021054.1643649-1-wangliang74@huawei.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants