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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 090666d3cc90 Linux 6.1.177
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14d87789580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5aae664b2df43c2
dashboard link: https://syzkaller.appspot.com/bug?extid=9001b74cb0866593a150
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0a97b9de9f21/disk-090666d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/40f470f8fbd0/vmlinux-090666d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/baabfa2bfd44/bzImage-090666d3.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-.... } 2670 jiffies s: 1033 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4401 Comm: syz.1.15 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:migrate_disable+0x62/0x180 kernel/sched/core.c:2225
Code: 0f b7 2b 66 85 ed 74 18 ff c5 43 0f b6 44 25 00 84 c0 0f 85 b8 00 00 00 66 89 2b e9 82 00 00 00 bf 01 00 00 00 e8 6e cb ff ff <e8> 89 6d d7 08 41 89 c6 83 f8 08 0f 83 b1 00 00 00 4e 8d 3c f5 80
RSP: 0018:ffffc900001e0788 EFLAGS: 00000002
RAX: 0000000000000102 RBX: ffff88801dba2238 RCX: ffffffff96c17103
RDX: 0000000000000100 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 0000000000000000 R08: dffffc0000000000 R09: 1ffffffff2162048
R10: dffffc0000000000 R11: fffffbfff2162049 R12: dffffc0000000000
R13: 1ffff11003b74447 R14: ffff888028e09b00 R15: 0000000000000000
FS: 00007fa3014336c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa301412d58 CR3: 0000000079109000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
bpf_prog_run_array include/linux/bpf.h:1663 [inline]
trace_call_bpf+0x227/0x6b0 kernel/trace/bpf_trace.c:135
perf_trace_run_bpf_submit+0x79/0x1c0 kernel/events/core.c:10027
perf_trace_preemptirq_template+0x268/0x320 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+0x7f/0x510 kernel/rcu/tree_plugin.h:685
Code: eb 03 48 b8 f1 f1 f1 f1 f8 f2 f2 f2 4a 89 04 2b 42 c7 44 2b 08 f8 f3 f3 f3 65 44 8b 35 52 82 95 7e 41 f7 c6 00 00 f0 00 74 40 <48> c7 44 24 40 0e 36 e0 45 4a c7 04 2b 00 00 00 00 42 c7 44 2b 08
RSP: 0018:ffffc900001e0ae0 EFLAGS: 00000206
RAX: 7f5beb6dd1f5d300 RBX: 1ffff9200003c164 RCX: 7f5beb6dd1f5d300
RDX: dffffc0000000000 RSI: ffffffff8a8c17a0 RDI: ffffffff8adf42e0
RBP: ffffc900001e0bd0 R08: ffff8880b8f3580b R09: 1ffff110171e6b01
R10: dffffc0000000000 R11: ffffed10171e6b02 R12: 0000000000000246
R13: dffffc0000000000 R14: ffff8880b8f3bb00 R15: 0000000000000002
__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:1751 [inline]
__hrtimer_run_queues+0x522/0xc90 kernel/time/hrtimer.c:1815
hrtimer_run_softirq+0x173/0x290 kernel/time/hrtimer.c:1832
handle_softirqs+0x291/0x910 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x13b/0x230 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:truncate_inode_pages_range+0xda2/0x10b0 mm/truncate.c:458
Code: 01 20 00 00 00 00 c7 44 01 28 00 00 00 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 c0 01 00 00 75 0f 48 8d 65 d8 5b 41 5c 41 5d <41> 5e 41 5f 5d c3 e8 93 b7 7e 08 e8 0e 8f d0 ff be 00 10 00 00 48
RSP: 0018:ffffc900046e7d40 EFLAGS: 00000246
RAX: 7f5beb6dd1f5d300 RBX: ffff8880729a54c0 RCX: 1ffff920008dcf74
RDX: f8f8f8f8f8f8f8f8 RSI: 000000000000e31a RDI: 000000000000e31b
RBP: ffffc900046e7d50 R08: ffff8880729a58af R09: 1ffff1100e534b15
R10: dffffc0000000000 R11: ffffed100e534b16 R12: dffffc0000000000
R13: ffff8880729a5598 R14: ffff8880729a5738 R15: ffff8880729a56e8
evict+0x4c9/0x8b0 fs/inode.c:707
__sys_socketpair+0x4fb/0x540 net/socket.c:-1
__do_sys_socketpair net/socket.c:1786 [inline]
__se_sys_socketpair net/socket.c:1783 [inline]
__x64_sys_socketpair+0x97/0xb0 net/socket.c:1783
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa30059de99
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa301433028 EFLAGS: 00000246 ORIG_RAX: 0000000000000035
RAX: ffffffffffffffda RBX: 00007fa300825fa0 RCX: 00007fa30059de99
RDX: 0000000000000005 RSI: 0000000000000003 RDI: 0000000000000002
RBP: 00007fa300633eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000240 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa300826038 R14: 00007fa300825fa0 R15: 00007ffeec61be48
</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