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

0 views
Skip to first unread message

syzbot

unread,
May 10, 2026, 4:40:39 PM (9 hours ago) May 10
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3b9f64db0496 Linux 6.6.138
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1108bdba580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5b35c4db8465904
dashboard link: https://syzkaller.appspot.com/bug?extid=e56fb7f0a6923e2175ba
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/9e5afbe648d5/disk-3b9f64db.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c3607dd9b93c/vmlinux-3b9f64db.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f0392d8b3ded/bzImage-3b9f64db.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P5138/1:b..l P6585/1:b..l
rcu: (detected by 0, t=10502 jiffies, g=29341, q=281 ncpus=2)
task:syz-executor state:R running task stack:21576 pid:6585 ppid:6569 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
preempt_schedule_common+0x82/0xc0 kernel/sched/core.c:6867
preempt_schedule+0xc0/0xd0 kernel/sched/core.c:6891
preempt_schedule_thunk+0x1a/0x30 arch/x86/entry/thunk_64.S:45
__raw_spin_unlock include/linux/spinlock_api_smp.h:143 [inline]
_raw_spin_unlock+0x3a/0x40 kernel/locking/spinlock.c:186
spin_unlock include/linux/spinlock.h:391 [inline]
copy_pte_range mm/memory.c:1107 [inline]
copy_pmd_range mm/memory.c:1168 [inline]
copy_pud_range mm/memory.c:1205 [inline]
copy_p4d_range mm/memory.c:1229 [inline]
copy_page_range+0x2ba0/0x3670 mm/memory.c:1323
dup_mmap kernel/fork.c:768 [inline]
dup_mm kernel/fork.c:1693 [inline]
copy_mm+0x1281/0x1d80 kernel/fork.c:1742
copy_process+0x16f7/0x3d80 kernel/fork.c:2507
kernel_clone+0x24b/0x8a0 kernel/fork.c:2915
__do_sys_clone kernel/fork.c:3058 [inline]
__se_sys_clone kernel/fork.c:3042 [inline]
__x64_sys_clone+0x1b7/0x230 kernel/fork.c:3042
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f25af3c5852
RSP: 002b:00007ffc5b24ac10 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffc5b24ac10 RCX: 00007f25af3c5852
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007ffc5b24ad9c R08: 0000000000000000 R09: 0000000000000001
R10: 00005555773387d0 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000000927c0 R14: 000000000004fef2 R15: 00007ffc5b24adf0
</TASK>
task:udevd state:R running task stack:25032 pid:5138 ppid:1 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
preempt_schedule_irq+0xbf/0x150 kernel/sched/core.c:7010
irqentry_exit+0x67/0x70 kernel/entry/common.c:438
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:687
RIP: 0010:arch_static_branch arch/x86/include/asm/jump_label.h:27 [inline]
RIP: 0010:static_key_false include/linux/jump_label.h:207 [inline]
RIP: 0010:trace_lock_acquire include/trace/events/lock.h:24 [inline]
RIP: 0010:lock_acquire+0x8a/0x420 kernel/locking/lockdep.c:5725
Code: 8c 48 c7 44 24 70 30 2a 68 81 4c 8d 64 24 60 49 c1 ec 03 48 b8 f1 f1 f1 f1 f8 f2 f2 f2 4b 89 04 3c 43 c7 44 3c 08 f8 f3 f3 f3 <0f> 1f 44 00 00 65 8b 05 06 8b 9b 7e 83 f8 08 0f 83 a0 01 00 00 41
RSP: 0018:ffffc900032876e0 EFLAGS: 00000a06
RAX: f2f2f2f8f1f1f1f1 RBX: 0000000000000000 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8d1320e0
RBP: ffffc900032877f0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000000 R12: 1ffff92000650ee8
R13: ffffffff8d1320e0 R14: 00007fccf4111b0a R15: dffffc0000000000
rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
rcu_read_lock include/linux/rcupdate.h:786 [inline]
is_bpf_text_address+0x47/0x2a0 kernel/bpf/core.c:741
kernel_text_address+0xa0/0xd0 kernel/extable.c:125
__kernel_text_address+0xd/0x30 kernel/extable.c:79
unwind_get_return_address+0x5d/0xc0 arch/x86/kernel/unwind_orc.c:369
arch_stack_walk+0x11d/0x190 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0xaa/0x100 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:53
__kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:329
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4b0 mm/slab.h:767
slab_alloc_node mm/slub.c:3495 [inline]
slab_alloc mm/slub.c:3503 [inline]
__kmem_cache_alloc_lru mm/slub.c:3510 [inline]
kmem_cache_alloc+0x11a/0x2d0 mm/slub.c:3519
getname_flags+0xbb/0x500 fs/namei.c:140
vfs_fstatat+0x111/0x1b0 fs/stat.c:298
__do_sys_newfstatat fs/stat.c:463 [inline]
__se_sys_newfstatat fs/stat.c:457 [inline]
__x64_sys_newfstatat+0x149/0x1f0 fs/stat.c:457
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fccf4111b0a
RSP: 002b:00007ffcb7212318 EFLAGS: 00000246 ORIG_RAX: 0000000000000106
RAX: ffffffffffffffda RBX: 00007ffcb72127b0 RCX: 00007fccf4111b0a
RDX: 00007ffcb7212320 RSI: 00007ffcb72127b0 RDI: 00000000ffffff9c
RBP: 000055eef6b8b910 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffcb72123b0
R13: 00000000000000fe R14: 000055eed0649be0 R15: 00007ffcb7212eb0
</TASK>
rcu: rcu_preempt kthread starved for 10452 jiffies! g29341 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:26632 pid:17 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_timeout+0x188/0x2d0 kernel/time/timer.c:2168
rcu_gp_fqs_loop+0x313/0x1590 kernel/rcu/tree.c:1667
rcu_gp_kthread+0x9d/0x3b0 kernel/rcu/tree.c:1866
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:pv_native_safe_halt+0xf/0x10 arch/x86/kernel/paravirt.c:148
Code: 19 21 02 c3 cc cc cc cc cc cc cc f3 0f 1e fa 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 66 90 0f 00 2d e3 d3 41 00 fb f4 <c3> 66 0f 1f 00 55 41 57 41 56 41 54 53 50 8b 2f eb 2e 41 89 de 80
RSP: 0018:ffffc90000187de0 EFLAGS: 000002c6
RAX: 06ef763aab340000 RBX: ffffffff8162a8f1 RCX: 06ef763aab340000
RDX: 0000000000000001 RSI: ffffffff8acac9e0 RDI: ffffffff8b1c8fa0
RBP: ffffc90000187f20 R08: ffff8880b8f36b2b R09: 1ffff110171e6d65
R10: dffffc0000000000 R11: ffffed10171e6d66 R12: 1ffff92000030fc8
R13: dffffc0000000000 R14: 1ffff1100344e780 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f25b01456b8 CR3: 000000006a6d2000 CR4: 00000000003526e0
Call Trace:
<TASK>
arch_safe_halt arch/x86/include/asm/paravirt.h:108 [inline]
default_idle+0x13/0x20 arch/x86/kernel/process.c:753
default_idle_call+0x6c/0xa0 kernel/sched/idle.c:97
cpuidle_idle_call kernel/sched/idle.c:178 [inline]
do_idle+0x221/0x590 kernel/sched/idle.c:302
cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:401
start_secondary+0xee/0xf0 arch/x86/kernel/smpboot.c:323
secondary_startup_64_no_verify+0x179/0x17b
</TASK>
sched: RT throttling activated


---
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