[v6.1] INFO: rcu detected stall in irqentry_exit (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1296a60a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=1b306ab260d4a04ebdc1
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fc2b42580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d8305ca1c94/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8bc85383c07b/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d337081bce56/bzImage-f6e38ae6.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 2676 jiffies s: 16201 root: 0x1/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8783 Comm: syz.1.4118 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:lock_release+0x4f/0x910 kernel/locking/lockdep.c:5670
Code: 04 25 28 00 00 00 48 89 84 24 c0 00 00 00 49 bd 00 00 00 00 00 fc ff df 48 c7 44 24 60 b3 8a b5 41 48 c7 44 24 68 9d a4 41 8c <48> c7 44 24 70 c0 79 63 81 4c 8d 7c 24 60 49 c1 ef 03 48 b8 f1 f1
RSP: 0018:ffffc900000071c0 EFLAGS: 00000086
RAX: 0fa35fec4cd89400 RBX: 0000000000000000 RCX: ffff88807ce8bb80
RDX: 0000000000000100 RSI: ffffffff81a70e7c RDI: ffffffff8cb2aca0
RBP: ffffc900000072d0 R08: dffffc0000000000 R09: fffffbfff215c449
R10: fffffbfff215c449 R11: 1ffffffff215c448 R12: 1ffff92000000e6c
R13: dffffc0000000000 R14: ffffc90000007460 R15: dffffc0000000000
FS: 000055557364e500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000743d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__perf_output_begin kernel/events/ring_buffer.c:263 [inline]
perf_output_begin_forward+0x7e4/0xa80 kernel/events/ring_buffer.c:272
__perf_event_output kernel/events/core.c:7732 [inline]
perf_event_output_forward+0x179/0x2a0 kernel/events/core.c:7750
__perf_event_overflow+0x448/0x610 kernel/events/core.c:9496
perf_swevent_overflow kernel/events/core.c:9572 [inline]
perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9610
perf_tp_event+0x335/0xb60 kernel/events/core.c:10029
perf_trace_run_bpf_submit+0xf3/0x1c0 kernel/events/core.c:10002
perf_trace_preemptirq_template+0x287/0x330 include/trace/events/preemptirq.h:14
trace_irq_enable_rcuidle+0xd3/0x140 include/trace/events/preemptirq.h:40
trace_hardirqs_on+0x24/0x40 kernel/trace/trace_preemptirq.c:44
asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:728
RIP: 0010:rcu_read_unlock_special+0x84/0x500 kernel/rcu/tree_plugin.h:685
Code: f1 f1 f1 00 f2 f2 f2 4a 89 04 2b 66 42 c7 44 2b 09 f3 f3 42 c6 44 2b 0b f3 65 44 8b 35 ed 90 96 7e 41 f7 c6 00 00 f0 00 74 45 <48> c7 44 24 40 0e 36 e0 45 4a c7 04 2b 00 00 00 00 66 42 c7 44 2b
RSP: 0018:ffffc90000007aa0 EFLAGS: 00000206
RAX: 0fa35fec4cd89400 RBX: 1ffff92000000f5c RCX: 0fa35fec4cd89400
RDX: dffffc0000000000 RSI: ffffffff8a8c0580 RDI: ffffffff8adef760
RBP: ffffc90000007b90 R08: dffffc0000000000 R09: fffffbfff215c46b
R10: fffffbfff215c46b R11: 1ffffffff215c46a R12: 0000000000000246
R13: dffffc0000000000 R14: ffff8880b8e3b900 R15: 0000000000000001
__rcu_read_unlock+0x78/0xd0 kernel/rcu/tree_plugin.h:426
rcu_read_unlock include/linux/rcupdate.h:823 [inline]
ieee80211_iterate_active_interfaces_atomic+0x156/0x170 net/mac80211/util.c:826
mac80211_hwsim_beacon+0xb7/0x1b0 drivers/net/wireless/mac80211_hwsim.c:2147
__run_hrtimer kernel/time/hrtimer.c:1747 [inline]
__hrtimer_run_queues+0x554/0xd60 kernel/time/hrtimer.c:1811
hrtimer_run_softirq+0x183/0x2a0 kernel/time/hrtimer.c:1828
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:679
irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:preempt_schedule_irq+0xac/0x150 kernel/sched/core.c:6873
Code: 44 24 20 f6 44 24 21 02 74 0b 0f 0b 48 f7 03 08 00 00 00 74 70 bf 01 00 00 00 e8 0f 42 37 f7 e8 4a be 66 f7 fb bf 01 00 00 00 <e8> df b9 ff ff 48 c7 44 24 40 00 00 00 00 9c 8f 44 24 40 8b 44 24
RSP: 0018:ffffc900036d7c40 EFLAGS: 00000286
RAX: 0fa35fec4cd89400 RBX: 0000000000000000 RCX: 0fa35fec4cd89400
RDX: dffffc0000000000 RSI: ffffffff8a8c0580 RDI: 0000000000000001
RBP: ffffc900036d7ce0 R08: dffffc0000000000 R09: fffffbfff215c46b
R10: fffffbfff215c46b R11: 1ffffffff215c46a R12: 0000000000000000
R13: 0000000000000000 R14: dffffc0000000000 R15: 1ffff920006daf88
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:__do_sys_perf_event_open kernel/events/core.c:-1 [inline]
RIP: 0010:__se_sys_perf_event_open+0x1a6e/0x1e60 kernel/events/core.c:12378
Code: ec 02 00 00 48 8b 5c 24 28 48 89 df e8 bb 39 00 00 48 89 df e8 a3 42 00 00 49 8d 7d 48 e8 7a b9 7c 08 4c 89 ef e8 42 ac fe ff <48> 8b 7c 24 28 48 83 c7 48 e8 64 b9 7c 08 80 7c 24 24 00 74 07 e8
RSP: 0018:ffffc900036d7da0 EFLAGS: 00000246
RAX: 0fa35fec4cd89400 RBX: ffff888028df1000 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: ffffffff8a8c0580 RDI: 00000000ffffffff
RBP: ffffc900036d7f10 R08: dffffc0000000000 R09: fffffbfff215c46b
R10: fffffbfff215c46b R11: 1ffffffff215c46a R12: ffff88802eb0e780
R13: 0000000000000000 R14: ffff8880736de000 R15: 0000000000000000
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f6432b8f6c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff157c98c8 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007f6432de5fa0 RCX: 00007f6432b8f6c9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000140
RBP: 00007f6432c11f91 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6432de5fa0 R14: 00007f6432de5fa0 R15: 0000000000000005
</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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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