[v5.15] INFO: rcu detected stall in pipe_write (2)

0 views
Skip to first unread message

syzbot

unread,
Jun 18, 2026, 4:17:41 PM (14 hours ago) Jun 18
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: dc027a595035 Linux 5.15.209
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12d2ccfe580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=55e136f09f8f16894496
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3d51783ddbbf/disk-dc027a59.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b6879bfcdc05/vmlinux-dc027a59.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e4755824edc0/bzImage-dc027a59.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-....: (35 ticks this GP) idle=dcf/1/0x4000000000000002 softirq=26286/26286 fqs=2087
(detected by 1, t=10505 jiffies, g=36505, q=2144)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 10372 Comm: syz.9.1623 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:strlen+0x2e/0x60 lib/string.c:581
Code: 41 54 53 48 c7 c0 ff ff ff ff 49 be 00 00 00 00 00 fc ff df 48 89 fb 49 89 c7 48 89 d8 48 c1 e8 03 42 0f b6 04 30 84 c0 75 11 <48> ff c3 49 8d 47 01 42 80 7c 3f 01 00 75 de eb 19 89 d9 80 e1 07
RSP: 0018:ffffc90000006db8 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffffffff8a2c35c5 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8c31f360 RDI: ffffffff8a2c35c0
RBP: ffffc90000006ee0 R08: 0000000000000002 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1b140de R12: dffffc0000000000
R13: 1ffff92000000dc4 R14: dffffc0000000000 R15: 0000000000000004
FS: 00007fba67eac6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005652cbf750b8 CR3: 0000000074f78000 CR4: 00000000003506f0
DR0: 0000200000000300 DR1: 0000200000000300 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
trace_event_get_offsets_lock_acquire include/trace/events/lock.h:13 [inline]
perf_trace_lock_acquire+0xc6/0x3e0 include/trace/events/lock.h:13
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0x3d7/0x400 kernel/locking/lockdep.c:5594
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:313
rcu_read_lock include/linux/rcupdate.h:740 [inline]
__perf_output_begin kernel/events/ring_buffer.c:163 [inline]
perf_output_begin_forward+0xa5/0xa40 kernel/events/ring_buffer.c:271
__perf_event_output kernel/events/core.c:7804 [inline]
perf_event_output_forward+0x19b/0x2e0 kernel/events/core.c:7822
__perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
perf_tp_event+0x383/0xbf0 kernel/events/core.c:10047
perf_trace_run_bpf_submit+0xf3/0x1c0 kernel/events/core.c:10021
perf_trace_preemptirq_template+0x2aa/0x360 include/trace/events/preemptirq.h:14
trace_irq_enable_rcuidle+0x108/0x180 include/trace/events/preemptirq.h:40
trace_hardirqs_on+0x57/0x80 kernel/trace/trace_preemptirq.c:44
asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:713
RIP: 0010:rcu_read_unlock_special+0x7f/0x4a0 kernel/rcu/tree_plugin.h:674
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 f2 cc 9c 7e 41 f7 c6 00 00 f0 00 74 40 <48> c7 44 24 20 0e 36 e0 45 4a c7 04 2b 00 00 00 00 42 c7 44 2b 08
RSP: 0018:ffffc900000077c0 EFLAGS: 00000206
RAX: 1348219fc4dcd300 RBX: 1ffff92000000efc RCX: 1348219fc4dcd300
RDX: dffffc0000000000 RSI: ffffffff8a2b3180 RDI: ffffffff8a7a09c0
RBP: ffffc900000078a0 R08: ffffffff901d81c7 R09: 1ffffffff203b038
R10: dffffc0000000000 R11: fffffbfff203b039 R12: ffffffff8c323800
R13: dffffc0000000000 R14: 0000000000000246 R15: 0000000000000001
__rcu_read_unlock+0x78/0xd0 kernel/rcu/tree_plugin.h:422
rcu_read_unlock include/linux/rcupdate.h:772 [inline]
ndisc_send_skb+0xde0/0x1500 net/ipv6/ndisc.c:521
addrconf_rs_timer+0x2d1/0x630 net/ipv6/addrconf.c:3956
call_timer_fn+0x17b/0x540 kernel/time/timer.c:1648
expire_timers kernel/time/timer.c:1699 [inline]
__run_timers+0x53e/0x800 kernel/time/timer.c:1970
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1983
handle_softirqs+0x339/0x830 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:finish_lock_switch+0x134/0x280 kernel/sched/core.c:4804
Code: be ff ff ff ff e8 4c ee 68 08 85 c0 74 4a 4d 85 ff 75 66 0f 1f 44 00 00 48 89 df e8 f6 59 72 08 e8 f1 e6 2a 00 fb 48 83 c4 08 <5b> 41 5c 41 5d 41 5e 41 5f 5d c3 48 89 df e8 c9 09 fe ff 43 80 3c
RSP: 0018:ffffc900014ef848 EFLAGS: 00000286
RAX: 1348219fc4dcd300 RBX: ffff8880b903a340 RCX: 1348219fc4dcd300
RDX: dffffc0000000000 RSI: ffffffff8a2b3180 RDI: ffffffff8a7a09c0
RBP: 1ffff11017207613 R08: ffff8880b903b30b R09: 1ffff11017207661
R10: dffffc0000000000 R11: ffffed1017207662 R12: 1ffff110172075c1
R13: dffffc0000000000 R14: ffff8880b903ae08 R15: 0000000000000000
finish_task_switch+0x12f/0x640 kernel/sched/core.c:4921
context_switch kernel/sched/core.c:5052 [inline]
__schedule+0x11f7/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
pipe_write+0xd5f/0x1aa0 fs/pipe.c:575
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x745/0xd60 fs/read_write.c:594
ksys_write+0x152/0x260 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fba69c52e59
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:00007fba67eac028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fba69ecbfa0 RCX: 00007fba69c52e59
RDX: 00000000fffffdef RSI: 00002000000001c0 RDI: 0000000000000000
RBP: 00007fba69ce8e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fba69ecc038 R14: 00007fba69ecbfa0 R15: 00007ffd7f6cca58
</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
Reply all
Reply to author
Forward
0 new messages