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

0 views
Skip to first unread message

syzbot

unread,
Jun 23, 2026, 11:18:37 AM (19 hours ago) Jun 23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d1cfde2d5d15 Linux 6.6.143
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c3d766580000
kernel config: https://syzkaller.appspot.com/x/.config?x=441765643cbfb8d
dashboard link: https://syzkaller.appspot.com/bug?extid=af4540caba043c274f7f
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4e37bcd98892/disk-d1cfde2d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/64b2ed856057/vmlinux-d1cfde2d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0a6949479d66/bzImage-d1cfde2d.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (1 GPs behind) idle=4d2c/1/0x4000000000000000 softirq=70097/70098 fqs=0
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P16308/3:b..l
rcu: (detected by 0, t=10502 jiffies, g=102861, q=17 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 16312 Comm: syz.6.2812 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:variable_test_bit arch/x86/include/asm/bitops.h:228 [inline]
RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:240 [inline]
RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]
RIP: 0010:__lock_acquire+0xd9c/0x7d80 kernel/locking/lockdep.c:5107
Code: 24 30 75 3c 48 63 d8 48 89 d8 48 c1 e8 06 48 8d 3c c5 00 c5 1b 91 be 08 00 00 00 e8 de 45 77 00 49 b8 00 00 00 00 00 fc ff df <48> 0f a3 1d 4c af b3 0f 48 8b 9c 24 88 00 00 00 0f 83 72 0a 00 00
RSP: 0018:ffffc900001f08e0 EFLAGS: 00000056
RAX: 0000000000000001 RBX: 0000000000000e59 RCX: ffffffff816815a2
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff911bc6c8
RBP: ffffc900001f0b28 R08: dffffc0000000000 R09: 1ffffffff22378d9
R10: dffffc0000000000 R11: fffffbfff22378da R12: 0000000000000000
R13: ffff888026feda00 R14: 0000000000000000 R15: ffff888026fee500
FS: 00007f0148a726c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c306ab2 CR3: 0000000026101000 CR4: 00000000003506e0
Call Trace:
<IRQ>
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
advance_sched+0xbb/0xc70 net/sched/sch_taprio.c:940
__run_hrtimer kernel/time/hrtimer.c:1754 [inline]
__hrtimer_run_queues+0x525/0xc10 kernel/time/hrtimer.c:1818
hrtimer_interrupt+0x39d/0x980 kernel/time/hrtimer.c:1880
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1077 [inline]
__sysvec_apic_timer_interrupt+0xfb/0x3b0 arch/x86/kernel/apic/apic.c:1094
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1088 [inline]
sysvec_apic_timer_interrupt+0x9f/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:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xc0/0x120 kernel/locking/spinlock.c:194
Code: c7 44 24 20 00 00 00 00 9c 8f 44 24 20 f7 44 24 20 00 02 00 00 41 c6 04 07 f8 75 4b f7 c3 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 4b e4 ce f6 65 8b 05 1c 33 76 75 85 c0 74 3c 48 c7 04 24 0e 36
RSP: 0018:ffffc9000484fc80 EFLAGS: 00000206
RAX: dffffc0000000004 RBX: 0000000000000a06 RCX: c3f1f113833c7b00
RDX: dffffc0000000000 RSI: ffffffff8acacb60 RDI: 0000000000000001
RBP: ffffc9000484fd10 R08: ffffffff8e8ae5ef R09: 1ffffffff1d15cbd
R10: dffffc0000000000 R11: fffffbfff1d15cbe R12: dffffc0000000000
R13: dffffc0000000000 R14: ffffffff8d14b5c0 R15: 1ffff92000909f90
do_settimeofday64+0x591/0x750 kernel/time/timekeeping.c:1342
__do_sys_clock_settime kernel/time/posix-timers.c:1130 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1114 [inline]
__x64_sys_clock_settime+0x25e/0x2a0 kernel/time/posix-timers.c:1114
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0147b9ce59
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:00007f0148a72028 EFLAGS: 00000246 ORIG_RAX: 00000000000000e3
RAX: ffffffffffffffda RBX: 00007f0147e15fa0 RCX: 00007f0147b9ce59
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000000
RBP: 00007f0147c32e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0147e16038 R14: 00007f0147e15fa0 R15: 00007ffd3d418408
</TASK>
task:syz.2.2813 state:R running task stack:27048 pid:16308 ppid:5783 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 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]
filemap_map_pages+0x1279/0x19c0 mm/filemap.c:3675
do_fault_around mm/memory.c:4595 [inline]
do_read_fault mm/memory.c:4628 [inline]
do_fault mm/memory.c:4775 [inline]
do_pte_missing mm/memory.c:3689 [inline]
handle_pte_fault mm/memory.c:5047 [inline]
__handle_mm_fault mm/memory.c:5188 [inline]
handle_mm_fault+0x384b/0x4a50 mm/memory.c:5353
do_user_addr_fault+0xad2/0x12d0 arch/x86/mm/fault.c:1322
handle_page_fault arch/x86/mm/fault.c:1463 [inline]
exc_page_fault+0x64/0x100 arch/x86/mm/fault.c:1516
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f9cdd671756
RSP: 002b:00007ffd92ddf250 EFLAGS: 00010202
RAX: 000000110c2f4000 RBX: ffffffff8a70302b RCX: 0000000000000005
RDX: 000000000000102b RSI: 00000000000000c0 RDI: 0000000000000020
RBP: 0000000000000000 R08: 00007f9cdda00000 R09: 00007f9cdda02000
R10: 000000008a70302f R11: 0000000000000000 R12: 00007f9cdda16038
R13: 0000000000000047 R14: ffffffff8a7030c1 R15: 00007f9cde545720
</TASK>
rcu: rcu_preempt kthread starved for 10502 jiffies! g102861 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
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:27032 pid:17 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 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+0x30d/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:
CPU: 0 PID: 5066 Comm: kworker/u4:10 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:csd_lock_wait kernel/smp.c:311 [inline]
RIP: 0010:smp_call_function_many_cond+0xd8a/0x1190 kernel/smp.c:855
Code: 89 f6 83 e6 01 31 ff e8 34 f1 0a 00 41 83 e6 01 49 be 00 00 00 00 00 fc ff df 75 07 e8 6f ed 0a 00 eb 38 f3 90 42 0f b6 04 33 <84> c0 75 11 41 f7 04 24 01 00 00 00 74 1e e8 53 ed 0a 00 eb e4 44
RSP: 0018:ffffc9000fc27780 EFLAGS: 00000293
RAX: 0000000000000000 RBX: 1ffff110171e82bd RCX: ffff888031fb5a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000fc27900 R08: ffffffff911bc507 R09: 1ffffffff22378a0
R10: dffffc0000000000 R11: fffffbfff22378a1 R12: ffff8880b8f415e8
R13: ffff8880b8e3d3c0 R14: dffffc0000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c2f60e0 CR3: 000000000cf32000 CR4: 00000000003506f0
DR0: 0000000000000101 DR1: 0000000000000007 DR2: 000000000000000f
DR3: 0000000000000006 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
on_each_cpu_cond_mask+0x3f/0x80 kernel/smp.c:1022
on_each_cpu include/linux/smp.h:71 [inline]
text_poke_sync arch/x86/kernel/alternative.c:2222 [inline]
text_poke_bp_batch+0x31e/0x980 arch/x86/kernel/alternative.c:2432
text_poke_flush arch/x86/kernel/alternative.c:2623 [inline]
text_poke_finish+0x30/0x50 arch/x86/kernel/alternative.c:2630
arch_jump_label_transform_apply+0x1c/0x30 arch/x86/kernel/jump_label.c:146
static_key_enable_cpuslocked+0x123/0x240 kernel/jump_label.c:207
static_key_enable+0x1a/0x20 kernel/jump_label.c:220
toggle_allocation_gate+0xa8/0x260 mm/kfence/core.c:847
process_one_work kernel/workqueue.c:2653 [inline]
process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2730
worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2811
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>


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