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

0 views
Skip to first unread message

syzbot

unread,
Feb 10, 2026, 3:38:39 PM (20 hours ago) Feb 10
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0182cb5b74ee Linux 6.1.162
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c8365a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=01daf404a1fed3f63ccf
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c8365a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d39b22580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8b6fc106fd9c/disk-0182cb5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f9ed1286c8af/vmlinux-0182cb5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/10c7fc900d05/bzImage-0182cb5b.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-.... } 2655 jiffies s: 3553 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: 4586 Comm: syz.3.80 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
RIP: 0010:asm_sysvec_irq_work+0x0/0x20 arch/x86/include/asm/idtentry.h:722
Code: e9 b5 03 00 00 90 90 90 90 90 0f 01 ca fc 6a ff e8 b5 02 00 00 48 89 c4 48 89 e7 e8 9a 60 ec ff e9 95 03 00 00 90 90 90 90 90 <0f> 01 ca fc 6a ff e8 95 02 00 00 48 89 c4 48 89 e7 e8 6a 65 ec ff
RSP: 0018:ffffc900001e0998 EFLAGS: 00000006
RAX: e3f024cdbb7c7700 RBX: 1ffff9200003c140 RCX: e3f024cdbb7c7700
RDX: dffffc0000000000 RSI: ffffffff8a8c1220 RDI: ffffffff8adf0d20
RBP: ffffc900001e0ac0 R08: ffff8880b8f3580b R09: 1ffff110171e6b01
R10: dffffc0000000000 R11: ffffed10171e6b02 R12: 0000000000000246
R13: dffffc0000000000 R14: ffff8880b8f3b900 R15: 0000000000000002
FS: 000055556677c500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe55369e60 CR3: 000000005e619000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
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 92 31 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:ffffc900001e09c0 EFLAGS: 00000206
__rcu_read_unlock+0x78/0xd0 kernel/rcu/tree_plugin.h:426
rcu_read_unlock include/linux/rcupdate.h:823 [inline]
process_backlog+0x410/0x6f0 net/core/dev.c:6037
__napi_poll+0xc0/0x460 net/core/dev.c:6603
napi_poll net/core/dev.c:6670 [inline]
net_rx_action+0x5dd/0xb20 net/core/dev.c:6784
handle_softirqs+0x2a1/0x930 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:__kasan_record_aux_stack+0x9f/0xc0 mm/kasan/generic.c:485
Code: 0f af f0 48 01 fe 49 39 f6 77 03 4c 89 f6 4c 89 ff e8 75 2a ff ff 49 63 8f bc 00 00 00 48 85 c9 74 1e 48 01 c8 74 19 8b 48 08 <89> 48 0c 0f b6 f3 bf 00 08 00 00 48 89 c3 e8 4e dc ff ff 89 43 08
RSP: 0018:ffffc90003cf7ce0 EFLAGS: 00000286
RAX: ffff888024e53d48 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff888024e53b80 RDI: ffff888140009a00
RBP: ffffc90003cf7da8 R08: 0000000000000280 R09: 1ffffffff1c3f96d
R10: dffffc0000000000 R11: fffffbfff1c3f96e R12: ffff88802ff99dc0
R13: dffffc0000000000 R14: ffff888024e53b80 R15: ffff888140009a00
task_work_add+0x7f/0x330 kernel/task_work.c:48
fput+0xd9/0x1a0 fs/file_table.c:376
filp_close+0x108/0x150 fs/open.c:1439
__range_close fs/file.c:703 [inline]
__close_range+0x58b/0x780 fs/file.c:753
__do_sys_close_range fs/open.c:1478 [inline]
__se_sys_close_range fs/open.c:1475 [inline]
__x64_sys_close_range+0x76/0x80 fs/open.c:1475
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:0x7f947df9bf79
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:00007fff169eaf18 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: ffffffffffffffda RBX: 00007fff169eb000 RCX: 00007f947df9bf79
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000017d2d R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b2f120000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f947e215fac R14: 00007f947e215fa8 R15: 00007f947e215fa0
</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
Reply all
Reply to author
Forward
0 new messages