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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 48d525b0e463 Linux 6.1.103
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=115080ed980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2fb3032ebb754b2c
dashboard link: https://syzkaller.appspot.com/bug?extid=3ced243d0bc525e3531b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/07f111bf78d8/disk-48d525b0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99cfdc824bac/vmlinux-48d525b0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86360d7c4c73/bzImage-48d525b0.xz

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

eth0: bad gso: type: 1, size: 1408
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P46/1:b..l
(detected by 1, t=10502 jiffies, g=22217, q=203 ncpus=2)
task:kworker/u4:3 state:R running task stack:20672 pid:46 ppid:2 flags:0x00004000
Workqueue: phy14 ieee80211_iface_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6558
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:ieee80211_sta_get_rates+0x3b5/0x720 net/mac80211/util.c:2195
Code: 98 00 00 00 4b 8d 5c bd 04 48 89 d8 48 c1 e8 03 49 bf 00 00 00 00 00 fc ff df 42 0f b6 04 38 84 c0 0f 85 fe 00 00 00 0f b7 1b <83> 7c 24 2c 1f 0f 87 29 01 00 00 e8 6b 26 5b f7 4d 89 e5 03 5c 24
RSP: 0018:ffffc90000b77840 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000014 RCX: dffffc0000000000
RDX: ffff8880192a0000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8a2f79f7 R09: fffffbfff1d33896
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88802228b350
R13: ffff88802228deb8 R14: 0000000000000001 R15: dffffc0000000000
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+0x1137/0x2dd0 net/mac80211/ibss.c:1638
ieee80211_iface_process_skb net/mac80211/iface.c:1632 [inline]
ieee80211_iface_work+0x7aa/0xce0 net/mac80211/iface.c:1686
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: rcu_preempt kthread starved for 9829 jiffies! g22217 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:27064 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1965
rcu_gp_fqs_loop+0x2d2/0x1150 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3b0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 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:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.1.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:22 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:112 [inline]
RIP: 0010:acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:567
Code: 30 db f6 48 83 e3 08 0f 85 0b 01 00 00 4c 8d 74 24 20 e8 64 ef e1 f6 0f 1f 44 00 00 e8 6a 2c db f6 0f 00 2d e3 0e b8 00 fb f4 <4c> 89 f3 48 c1 eb 03 42 80 3c 3b 00 74 08 4c 89 f7 e8 eb a8 32 f7
RSP: 0018:ffffc90000177b80 EFLAGS: 000002d3
RAX: ffffffff8aaf7436 RBX: 0000000000000000 RCX: ffff888012b41dc0
RDX: 0000000000000000 RSI: ffffffff8b0c0260 RDI: ffffffff8b5d5de0
RBP: ffffc90000177c10 R08: ffffffff8aaf7418 R09: ffffed10025683b9
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff9200002ef70
R13: ffff888146e94804 R14: ffffc90000177ba0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffa0ffb16c0 CR3: 00000000794f4000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
acpi_idle_enter+0x352/0x4f0 drivers/acpi/processor_idle.c:704
cpuidle_enter_state+0x516/0xf80 drivers/cpuidle/cpuidle.c:239
cpuidle_enter+0x59/0x90 drivers/cpuidle/cpuidle.c:356
call_cpuidle kernel/sched/idle.c:155 [inline]
cpuidle_idle_call kernel/sched/idle.c:236 [inline]
do_idle+0x3ce/0x680 kernel/sched/idle.c:303
cpu_startup_entry+0x3d/0x60 kernel/sched/idle.c:401
start_secondary+0xe4/0xf0 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xcf/0xdb
</TASK>


---
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