[v5.15] INFO: rcu detected stall in sys_clock_settime (2)
0 views
Skip to first unread message
syzbot
May 5, 2026, 12:49:32 PM (20 hours ago) May 5
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ef251c45f1cd Linux 5.15.204
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13d8d76c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=61069fb15c7f6969fd52
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/bde897c3d01f/disk-ef251c45.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51b2a5826cd1/vmlinux-ef251c45.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb95a5a40121/bzImage-ef251c45.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+61069f...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (1 GPs behind) idle=045/1/0x4000000000000000 softirq=13353/13355 fqs=9
(detected by 0, t=10505 jiffies, g=18481, q=460)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5813 Comm: syz.5.294 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:cpumask_test_cpu include/linux/cpumask.h:344 [inline]
RIP: 0010:cpu_online include/linux/cpumask.h:895 [inline]
RIP: 0010:trace_lock_release include/trace/events/lock.h:58 [inline]
RIP: 0010:lock_release+0xa4/0x8a0 kernel/locking/lockdep.c:5634
Code: 44 00 00 65 8b 1d d4 81 a4 7e 83 fb 08 0f 83 4e 05 00 00 89 d8 c1 e8 06 48 8d 3c c5 28 f0 89 8d be 08 00 00 00 e8 4c c1 60 00 <89> d8 48 0f a3 05 7a 5c 2c 0c 73 0d e8 6b 4c 07 00 84 c0 0f 84 53
RSP: 0018:ffffc90000dd0b80 EFLAGS: 00000056
RAX: 0000000000000001 RBX: 0000000000000001 RCX: ffffffff815d93a4
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8d89f028
RBP: ffffc90000dd0c90 R08: ffffffff8d89f02f R09: 1ffffffff1b13e05
R10: dffffc0000000000 R11: fffffbfff1b13e06 R12: 1ffff920001ba17c
R13: dffffc0000000000 R14: ffff8880b912a240 R15: 1ffff920001ba194
FS: 00007f4c2f90e6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4c2f8ecff8 CR3: 0000000064ec1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
_raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
__run_hrtimer kernel/time/hrtimer.c:1681 [inline]
__hrtimer_run_queues+0x3fd/0xb70 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x3bb/0x8d0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1097 [inline]
__sysvec_apic_timer_interrupt+0x137/0x4a0 arch/x86/kernel/apic/apic.c:1114
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0x9b/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:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xbc/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> 5f 39 8c f7 65 8b 05 f0 36 3c 76 85 c0 74 3c 48 c7 04 24 0e 36
RSP: 0018:ffffc900048b7c80 EFLAGS: 00000206
RAX: dffffc0000000004 RBX: 0000000000000a06 RCX: 1eb8aa27cc2d4000
RDX: dffffc0000000000 RSI: ffffffff8a2b2800 RDI: 0000000000000001
RBP: ffffc900048b7d10 R08: ffffffff8c330f83 R09: 1ffffffff18661f0
R10: dffffc0000000000 R11: fffffbfff18661f1 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffffffff8c330f80 R15: 1ffff92000916f90
do_settimeofday64+0x5ac/0x760 kernel/time/timekeeping.c:1325
__do_sys_clock_settime kernel/time/posix-timers.c:1125 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1113 [inline]
__x64_sys_clock_settime+0x25a/0x2a0 kernel/time/posix-timers.c:1113
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:0x7f4c316b4dd9
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:00007f4c2f90e028 EFLAGS: 00000246 ORIG_RAX: 00000000000000e3
RAX: ffffffffffffffda RBX: 00007f4c3192dfa0 RCX: 00007f4c316b4dd9
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000000000000000
RBP: 00007f4c3174ad69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4c3192e038 R14: 00007f4c3192dfa0 R15: 00007ffdd327d708
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10459 jiffies! g18481 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=10947
rcu: rcu_preempt kthread starved for 10460 jiffies! g18481 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->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:I stack:27800 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0x184/0x2d0 kernel/time/timer.c:2117
rcu_gp_fqs_loop+0x2be/0x11d0 kernel/rcu/tree.c:1972
rcu_gp_kthread+0x9b/0x370 kernel/rcu/tree.c:2145
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
NMI backtrace for cpu 0
CPU: 0 PID: 4289 Comm: kworker/u4:10 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: writeback wb_workfn (flush-8:0)
Call Trace:
<IRQ>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_check_gp_kthread_starvation+0x1cd/0x250 kernel/rcu/tree_stall.h:487
print_other_cpu_stall+0x1110/0x1270 kernel/rcu/tree_stall.h:592
check_cpu_stall kernel/rcu/tree_stall.h:745 [inline]
rcu_pending kernel/rcu/tree.c:3936 [inline]
rcu_sched_clock_irq+0x843/0x1120 kernel/rcu/tree.c:2619
update_process_times+0x193/0x200 kernel/time/timer.c:2021
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x37d/0x560 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x4b4/0xb70 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x3bb/0x8d0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1097 [inline]
__sysvec_apic_timer_interrupt+0x137/0x4a0 arch/x86/kernel/apic/apic.c:1114
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0x9b/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:check_kcov_mode kernel/kcov.c:172 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x13/0x60 kernel/kcov.c:206
Code: 48 8b 3d d0 bd 10 0c 48 89 de 5b e9 27 55 44 00 00 00 cc cc 00 00 cc 48 8b 04 24 65 48 8b 0d 24 3b 89 7e 65 8b 15 25 3b 89 7e <81> e2 00 01 ff 00 74 11 81 fa 00 01 00 00 75 35 83 b9 34 16 00 00
RSP: 0018:ffffc9000321e678 EFLAGS: 00000202
RAX: ffffffff816dd568 RBX: 0000000000000001 RCX: ffff88802699bb80
RDX: 0000000000000003 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000321e7c0 R08: ffff8880b903b3d7 R09: 1ffff1101720767a
R10: dffffc0000000000 R11: ffffed101720767b R12: ffff8880b91405c8
R13: 1ffff110172280b9 R14: ffff8880b903b3c0 R15: 0000000000000001
csd_lock_wait kernel/smp.c:440 [inline]
smp_call_function_many_cond+0xbd8/0xd90 kernel/smp.c:969
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1134
__flush_tlb_multi arch/x86/include/asm/paravirt.h:87 [inline]
flush_tlb_multi arch/x86/mm/tlb.c:946 [inline]
flush_tlb_mm_range+0x365/0x580 arch/x86/mm/tlb.c:1034
flush_tlb_page arch/x86/include/asm/tlbflush.h:240 [inline]
ptep_clear_flush+0x112/0x140 mm/pgtable-generic.c:97
page_mkclean_one+0x1eb/0x3e0 mm/rmap.c:938
rmap_walk_file+0x408/0x610 mm/rmap.c:2378
rmap_walk mm/rmap.c:2396 [inline]
page_mkclean+0x2f4/0x400 mm/rmap.c:1006
clear_page_dirty_for_io+0x3f8/0x9f0 mm/page-writeback.c:2749
mpage_submit_page+0x8a/0x210 fs/ext4/inode.c:2095
mpage_process_page_bufs+0x6d8/0x8b0 fs/ext4/inode.c:2229
mpage_prepare_extent_to_map+0xbc2/0xfe0 fs/ext4/inode.c:2657
ext4_writepages+0xa9a/0x2df0 fs/ext4/inode.c:2785
do_writepages+0x476/0x6e0 mm/page-writeback.c:2386
__writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940
__writeback_inodes_wb+0x12a/0x3f0 fs/fs-writeback.c:2011
wb_writeback+0x46f/0xbe0 fs/fs-writeback.c:2116
wb_check_old_data_flush fs/fs-writeback.c:2216 [inline]
wb_do_writeback fs/fs-writeback.c:2269 [inline]
wb_workfn+0xb15/0xf20 fs/fs-writeback.c:2298
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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
syzbot found the following issue on:
HEAD commit: ef251c45f1cd Linux 5.15.204
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13d8d76c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=61069fb15c7f6969fd52
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/bde897c3d01f/disk-ef251c45.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51b2a5826cd1/vmlinux-ef251c45.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb95a5a40121/bzImage-ef251c45.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+61069f...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (1 GPs behind) idle=045/1/0x4000000000000000 softirq=13353/13355 fqs=9
(detected by 0, t=10505 jiffies, g=18481, q=460)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5813 Comm: syz.5.294 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:cpumask_test_cpu include/linux/cpumask.h:344 [inline]
RIP: 0010:cpu_online include/linux/cpumask.h:895 [inline]
RIP: 0010:trace_lock_release include/trace/events/lock.h:58 [inline]
RIP: 0010:lock_release+0xa4/0x8a0 kernel/locking/lockdep.c:5634
Code: 44 00 00 65 8b 1d d4 81 a4 7e 83 fb 08 0f 83 4e 05 00 00 89 d8 c1 e8 06 48 8d 3c c5 28 f0 89 8d be 08 00 00 00 e8 4c c1 60 00 <89> d8 48 0f a3 05 7a 5c 2c 0c 73 0d e8 6b 4c 07 00 84 c0 0f 84 53
RSP: 0018:ffffc90000dd0b80 EFLAGS: 00000056
RAX: 0000000000000001 RBX: 0000000000000001 RCX: ffffffff815d93a4
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8d89f028
RBP: ffffc90000dd0c90 R08: ffffffff8d89f02f R09: 1ffffffff1b13e05
R10: dffffc0000000000 R11: fffffbfff1b13e06 R12: 1ffff920001ba17c
R13: dffffc0000000000 R14: ffff8880b912a240 R15: 1ffff920001ba194
FS: 00007f4c2f90e6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4c2f8ecff8 CR3: 0000000064ec1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
_raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
__run_hrtimer kernel/time/hrtimer.c:1681 [inline]
__hrtimer_run_queues+0x3fd/0xb70 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x3bb/0x8d0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1097 [inline]
__sysvec_apic_timer_interrupt+0x137/0x4a0 arch/x86/kernel/apic/apic.c:1114
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0x9b/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:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xbc/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> 5f 39 8c f7 65 8b 05 f0 36 3c 76 85 c0 74 3c 48 c7 04 24 0e 36
RSP: 0018:ffffc900048b7c80 EFLAGS: 00000206
RAX: dffffc0000000004 RBX: 0000000000000a06 RCX: 1eb8aa27cc2d4000
RDX: dffffc0000000000 RSI: ffffffff8a2b2800 RDI: 0000000000000001
RBP: ffffc900048b7d10 R08: ffffffff8c330f83 R09: 1ffffffff18661f0
R10: dffffc0000000000 R11: fffffbfff18661f1 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffffffff8c330f80 R15: 1ffff92000916f90
do_settimeofday64+0x5ac/0x760 kernel/time/timekeeping.c:1325
__do_sys_clock_settime kernel/time/posix-timers.c:1125 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1113 [inline]
__x64_sys_clock_settime+0x25a/0x2a0 kernel/time/posix-timers.c:1113
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:0x7f4c316b4dd9
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:00007f4c2f90e028 EFLAGS: 00000246 ORIG_RAX: 00000000000000e3
RAX: ffffffffffffffda RBX: 00007f4c3192dfa0 RCX: 00007f4c316b4dd9
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000000000000000
RBP: 00007f4c3174ad69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4c3192e038 R14: 00007f4c3192dfa0 R15: 00007ffdd327d708
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10459 jiffies! g18481 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=10947
rcu: rcu_preempt kthread starved for 10460 jiffies! g18481 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->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:I stack:27800 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0x184/0x2d0 kernel/time/timer.c:2117
rcu_gp_fqs_loop+0x2be/0x11d0 kernel/rcu/tree.c:1972
rcu_gp_kthread+0x9b/0x370 kernel/rcu/tree.c:2145
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
NMI backtrace for cpu 0
CPU: 0 PID: 4289 Comm: kworker/u4:10 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: writeback wb_workfn (flush-8:0)
Call Trace:
<IRQ>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_check_gp_kthread_starvation+0x1cd/0x250 kernel/rcu/tree_stall.h:487
print_other_cpu_stall+0x1110/0x1270 kernel/rcu/tree_stall.h:592
check_cpu_stall kernel/rcu/tree_stall.h:745 [inline]
rcu_pending kernel/rcu/tree.c:3936 [inline]
rcu_sched_clock_irq+0x843/0x1120 kernel/rcu/tree.c:2619
update_process_times+0x193/0x200 kernel/time/timer.c:2021
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x37d/0x560 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x4b4/0xb70 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x3bb/0x8d0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1097 [inline]
__sysvec_apic_timer_interrupt+0x137/0x4a0 arch/x86/kernel/apic/apic.c:1114
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0x9b/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:check_kcov_mode kernel/kcov.c:172 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x13/0x60 kernel/kcov.c:206
Code: 48 8b 3d d0 bd 10 0c 48 89 de 5b e9 27 55 44 00 00 00 cc cc 00 00 cc 48 8b 04 24 65 48 8b 0d 24 3b 89 7e 65 8b 15 25 3b 89 7e <81> e2 00 01 ff 00 74 11 81 fa 00 01 00 00 75 35 83 b9 34 16 00 00
RSP: 0018:ffffc9000321e678 EFLAGS: 00000202
RAX: ffffffff816dd568 RBX: 0000000000000001 RCX: ffff88802699bb80
RDX: 0000000000000003 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000321e7c0 R08: ffff8880b903b3d7 R09: 1ffff1101720767a
R10: dffffc0000000000 R11: ffffed101720767b R12: ffff8880b91405c8
R13: 1ffff110172280b9 R14: ffff8880b903b3c0 R15: 0000000000000001
csd_lock_wait kernel/smp.c:440 [inline]
smp_call_function_many_cond+0xbd8/0xd90 kernel/smp.c:969
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1134
__flush_tlb_multi arch/x86/include/asm/paravirt.h:87 [inline]
flush_tlb_multi arch/x86/mm/tlb.c:946 [inline]
flush_tlb_mm_range+0x365/0x580 arch/x86/mm/tlb.c:1034
flush_tlb_page arch/x86/include/asm/tlbflush.h:240 [inline]
ptep_clear_flush+0x112/0x140 mm/pgtable-generic.c:97
page_mkclean_one+0x1eb/0x3e0 mm/rmap.c:938
rmap_walk_file+0x408/0x610 mm/rmap.c:2378
rmap_walk mm/rmap.c:2396 [inline]
page_mkclean+0x2f4/0x400 mm/rmap.c:1006
clear_page_dirty_for_io+0x3f8/0x9f0 mm/page-writeback.c:2749
mpage_submit_page+0x8a/0x210 fs/ext4/inode.c:2095
mpage_process_page_bufs+0x6d8/0x8b0 fs/ext4/inode.c:2229
mpage_prepare_extent_to_map+0xbc2/0xfe0 fs/ext4/inode.c:2657
ext4_writepages+0xa9a/0x2df0 fs/ext4/inode.c:2785
do_writepages+0x476/0x6e0 mm/page-writeback.c:2386
__writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940
__writeback_inodes_wb+0x12a/0x3f0 fs/fs-writeback.c:2011
wb_writeback+0x46f/0xbe0 fs/fs-writeback.c:2116
wb_check_old_data_flush fs/fs-writeback.c:2216 [inline]
wb_do_writeback fs/fs-writeback.c:2269 [inline]
wb_workfn+0xb15/0xf20 fs/fs-writeback.c:2298
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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