[v6.6] INFO: rcu detected stall in perf_release (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10b6469a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=efff49bb0ee448d970de
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=1659ffb4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125f2e22580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/857fe583cdec/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed4d3c1402bc/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40296d968c3d/bzImage-5fa4793a.xz

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

rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-....: (10472 ticks this GP) idle=22ec/1/0x4000000000000000 softirq=17574/18185 fqs=4543
rcu: hardirqs softirqs csw/system
rcu: number: 1955614 1456 0
rcu: cputime: 15870 36615 38 ==> 52490(ms)
rcu: (t=10500 jiffies g=21133 q=212 ncpus=2)
CPU: 0 PID: 7848 Comm: syz-executor262 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:slab_pre_alloc_hook+0x0/0x310 mm/slab.h:711
Code: c8 75 02 e9 3d fb ff ff 48 c7 c7 e0 b1 e2 8c 48 89 ee e8 83 c8 75 02 e9 f0 fd ff ff e8 a9 5f 24 ff e9 7c ff ff ff 0f 1f 40 00 <55> 41 57 41 56 41 55 41 54 53 48 83 ec 18 44 89 c5 49 89 cf 48 89
RSP: 0018:ffffc90000007868 EFLAGS: 00000246
RAX: ffffffff885c3835 RBX: 0000000000000000 RCX: 0000000000000001
RDX: ffffc90000007880 RSI: 0000000000000000 RDI: ffff88801d24d8c0
RBP: ffffc9000000791c R08: 0000000000082820 R09: 0000000000000000
R10: ffff88802346a8c0 R11: fffffbfff1c94426 R12: 00000000000000c0
R13: 00000000000002c0 R14: 0000000000082820 R15: ffff88801d24d8c0
FS: 000055555f793480(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000078aeb000 CR4: 00000000003506f0
Call Trace:
<IRQ>
slab_alloc_node mm/slub.c:3477 [inline]
kmem_cache_alloc_node+0x60/0x330 mm/slub.c:3540
kmalloc_reserve+0x95/0x240 net/core/skbuff.c:562
__alloc_skb+0x138/0x2c0 net/core/skbuff.c:653
__netdev_alloc_skb+0x10c/0x500 net/core/skbuff.c:717
netdev_alloc_skb include/linux/skbuff.h:3272 [inline]
dev_alloc_skb include/linux/skbuff.h:3285 [inline]
__ieee80211_beacon_get+0xe17/0x1600 net/mac80211/tx.c:5447
ieee80211_beacon_get_tim+0xb8/0x560 net/mac80211/tx.c:5569
ieee80211_beacon_get include/net/mac80211.h:5440 [inline]
mac80211_hwsim_beacon_tx+0x3c7/0x780 drivers/net/wireless/virtual/mac80211_hwsim.c:2265
__iterate_interfaces+0x243/0x500 net/mac80211/util.c:766
ieee80211_iterate_active_interfaces_atomic+0xdb/0x180 net/mac80211/util.c:802
mac80211_hwsim_beacon+0xbb/0x1b0 drivers/net/wireless/virtual/mac80211_hwsim.c:2295
__run_hrtimer kernel/time/hrtimer.c:1750 [inline]
__hrtimer_run_queues+0x51e/0xc40 kernel/time/hrtimer.c:1814
hrtimer_run_softirq+0x187/0x2b0 kernel/time/hrtimer.c:1831
handle_softirqs+0x280/0x820 kernel/softirq.c:578
__do_softirq kernel/softirq.c:612 [inline]
invoke_softirq kernel/softirq.c:452 [inline]
__irq_exit_rcu+0xc7/0x190 kernel/softirq.c:661
irq_exit_rcu+0x9/0x20 kernel/softirq.c:673
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1088 [inline]
sysvec_apic_timer_interrupt+0xa4/0xc0 arch/x86/kernel/apic/apic.c:1088
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:687
RIP: 0010:finish_task_switch+0x26a/0x920 kernel/sched/core.c:5254
Code: 0f 84 37 01 00 00 48 85 db 0f 85 56 01 00 00 0f 1f 44 00 00 4c 8b 75 d0 4c 89 e7 e8 80 ca 14 09 e8 4b a4 2f 00 fb 4c 8b 65 c0 <49> 8d bc 24 f8 15 00 00 48 89 f8 48 c1 e8 03 42 0f b6 04 28 84 c0
RSP: 0018:ffffc9000c35f9b8 EFLAGS: 00000286
RAX: d9a4bef203fe4800 RBX: 0000000000000000 RCX: d9a4bef203fe4800
RDX: dffffc0000000000 RSI: ffffffff8aaabce0 RDI: ffffffff8afc6f80
RBP: ffffc9000c35fa10 R08: ffffffff90d945df R09: 1ffffffff21b28bb
R10: dffffc0000000000 R11: fffffbfff21b28bc R12: ffff8880222d0000
R13: dffffc0000000000 R14: ffffffff8ca93440 R15: ffff8880b8e3cac8
context_switch kernel/sched/core.c:5383 [inline]
__schedule+0x14da/0x44d0 kernel/sched/core.c:6699
preempt_schedule_common+0x82/0xc0 kernel/sched/core.c:6866
preempt_schedule+0xab/0xc0 kernel/sched/core.c:6890
preempt_schedule_thunk+0x1a/0x30 arch/x86/entry/thunk_64.S:45
__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline]
_raw_spin_unlock_irq+0x40/0x50 kernel/locking/spinlock.c:202
perf_remove_from_context+0xdb/0x1d0 kernel/events/core.c:2448
perf_event_release_kernel+0x1de/0x8c0 kernel/events/core.c:5417
perf_release+0x3b/0x40 kernel/events/core.c:5511
__fput+0x234/0x970 fs/file_table.c:384
__do_sys_close fs/open.c:1573 [inline]
__se_sys_close+0x15f/0x220 fs/open.c:1558
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3b21e6b64a
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 83 83 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 e3 83 02 00 8b 44 24
RSP: 002b:00007ffee824c7e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f3b21e6b64a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000003
R10: ffffffffffffffff R11: 0000000000000293 R12: 00007ffee824c818
R13: 00007ffee824c830 R14: 00007ffee824c870 R15: 000000000000080a
</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