[v6.1] INFO: rcu detected stall in cfg80211_wiphy_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1989cd3d56e2 Linux 6.1.167
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13eed06a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=5c07d86ad5d5e3beb656
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/814271465bd5/disk-1989cd3d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bd559379c491/vmlinux-1989cd3d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/063c12bf8ba7/bzImage-1989cd3d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c07d8...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P20191/1:b..l P4326/1:b..l
(detected by 0, t=10502 jiffies, g=205521, q=58 ncpus=2)
task:kworker/u4:6 state:R running task stack:23152 pid:4326 ppid:2 flags:0x00004000
Workqueue: events_unbound cfg80211_wiphy_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
preempt_schedule_irq+0xbb/0x160 kernel/sched/core.c:6874
irqentry_exit+0x63/0x70 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x60 kernel/kcov.c:212
Code: 2e 0f 1f 84 00 00 00 00 00 90 53 48 89 fb e8 17 00 00 00 48 8b 3d 90 6c 9d 0c 48 89 de 5b e9 97 41 50 00 00 00 cc cc 00 00 cc <48> 8b 04 24 65 48 8b 0d a4 fa 7f 7e 65 8b 15 a5 fa 7f 7e 81 e2 00
RSP: 0018:ffffc900040c77f0 EFLAGS: 00000216
RAX: ffffffff89b38f2a RBX: 0000000000000008 RCX: 0000000000000000
RDX: ffff88802486d940 RSI: 000000000000006e RDI: 00000000000000f0
RBP: 00000000000000f0 R08: ffffffff8e1fdeef R09: 1ffffffff1c3fbdd
R10: dffffc0000000000 R11: fffffbfff1c3fbde R12: 000000000000000b
R13: 000000000000006e R14: dffffc0000000000 R15: ffff88807b703350
ieee80211_sta_get_rates+0x422/0x6b0 net/mac80211/util.c:2198
ieee80211_update_sta_info net/mac80211/ibss.c:1003 [inline]
ieee80211_rx_bss_info net/mac80211/ibss.c:1118 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1609 [inline]
ieee80211_ibss_rx_queued_mgmt+0x10ad/0x2cd0 net/mac80211/ibss.c:1638
ieee80211_iface_process_skb net/mac80211/iface.c:1679 [inline]
ieee80211_iface_work+0x726/0xc80 net/mac80211/iface.c:1733
cfg80211_wiphy_work+0x221/0x260 net/wireless/core.c:433
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
task:kworker/u4:26 state:R running task stack:23952 pid:20191 ppid:2 flags:0x00004000
Workqueue: events_unbound cfg80211_wiphy_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
preempt_schedule_irq+0xbb/0x160 kernel/sched/core.c:6874
irqentry_exit+0x63/0x70 kernel/entry/common.c:439
asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:682
RIP: 0010:ieee80211_sta_get_rates+0x362/0x6b0 net/mac80211/util.c:-1
Code: 4c 89 ff e8 20 f1 1f f8 48 63 c3 48 8d 2c 40 48 c1 e5 02 49 03 2f 48 89 e8 48 c1 e8 03 42 0f b6 04 30 84 c0 0f 85 f9 00 00 00 <44> 8b 75 00 44 0b 74 24 3c bf ff ff ff ff 44 89 f6 e8 28 e9 ce f7
RSP: 0018:ffffc9000400f7f8 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000008 RCX: ffff88802b660000
RDX: 0000000000000000 RSI: 0000000000000168 RDI: 00000000000000b4
RBP: ffff888067555f18 R08: ffffffff8e1fdeef R09: 1ffffffff1c3fbdd
R10: dffffc0000000000 R11: fffffbfff1c3fbde R12: 000000000000000b
R13: 0000000000000168 R14: dffffc0000000000 R15: ffff888067553350
ieee80211_update_sta_info net/mac80211/ibss.c:1003 [inline]
ieee80211_rx_bss_info net/mac80211/ibss.c:1118 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1609 [inline]
ieee80211_ibss_rx_queued_mgmt+0x10ad/0x2cd0 net/mac80211/ibss.c:1638
ieee80211_iface_process_skb net/mac80211/iface.c:1679 [inline]
ieee80211_iface_work+0x726/0xc80 net/mac80211/iface.c:1733
cfg80211_wiphy_work+0x221/0x260 net/wireless/core.c:433
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: rcu_preempt kthread starved for 9886 jiffies! g205521 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:27728 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0x184/0x2d0 kernel/time/timer.c:2168
rcu_gp_fqs_loop+0x303/0x1340 kernel/rcu/tree.c:1706
rcu_gp_kthread+0x99/0x3b0 kernel/rcu/tree.c:1905
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at default_idle+0xb/0x10 arch/x86/kernel/process.c:741


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup