[v5.15] INFO: rcu detected stall in sys_clock_settime

1 view
Skip to first unread message

syzbot

unread,
Jul 12, 2023, 11:09:13 PM7/12/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11cfcaa2a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c67dae6b27f0d6cd
dashboard link: https://syzkaller.appspot.com/bug?extid=b9b138957d968392c98d
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4aa2cbf1e81c/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ebee78b098c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e17f9ac4b6a/bzImage-d54cfc42.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (1 GPs behind) idle=245/1/0x4000000000000000 softirq=36129/36130 fqs=17
(detected by 1, t=10502 jiffies, g=49977, q=349)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 11095 Comm: syz-executor.0 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:separate_irq_context kernel/locking/lockdep.c:4540 [inline]
RIP: 0010:__lock_acquire+0xdf8/0x1ff0 kernel/locking/lockdep.c:4995
Code: 48 c1 e8 03 0f b6 04 38 84 c0 0f 85 87 0c 00 00 8b 1b 48 8b 44 24 38 0f b6 04 38 84 c0 0f 85 9b 0c 00 00 48 8b 44 24 20 33 18 <f7> c3 00 60 00 00 74 0f c7 44 24 2c 01 00 00 00 49 c7 c7 ff ff ff
RSP: 0018:ffffc90000007a60 EFLAGS: 00000002
RAX: ffff888023368b38 RBX: 00000000000f402f RCX: ffff888023368af0
RDX: 0000000000000000 RSI: 0000000000000008 RDI: dffffc0000000000
RBP: ffff888023368ae0 R08: dffffc0000000000 R09: fffffbfff1f7a621
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff888023368ae8 R14: 1ffff1100466d15c R15: 124e57aca902e35f
FS: 00007fe3ed0836c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe3eec22988 CR3: 000000001e6d7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:269
rcu_read_lock include/linux/rcupdate.h:696 [inline]
advance_sched+0x6ce/0x940 net/sched/sch_taprio.c:769
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x598/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
Code: 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 62 65 a4 f7 f6 44 24 21 02 75 4e 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 87 1a 32 f7 65 8b 05 88 66 dd 75 85 c0 74 3f 48 c7 04 24 0e 36
RSP: 0018:ffffc900055afb60 EFLAGS: 00000206
RAX: 9424b941ddeaf100 RBX: 1ffff92000ab5f70 RCX: ffffffff8162db08
RDX: dffffc0000000000 RSI: ffffffff8a8afd60 RDI: 0000000000000001
RBP: ffffc900055afbf0 R08: dffffc0000000000 R09: fffffbfff1f7a621
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000ab5f6c R14: ffffc900055afb80 R15: 0000000000000246
clock_was_set+0x67d/0x880 kernel/time/hrtimer.c:970
do_settimeofday64+0x673/0x7e0 kernel/time/timekeeping.c:1328
__do_sys_clock_settime kernel/time/posix-timers.c:1092 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1080 [inline]
__x64_sys_clock_settime+0x232/0x270 kernel/time/posix-timers.c:1080
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fe3eeb01b29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe3ed0830c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e3
RAX: ffffffffffffffda RBX: 00007fe3eec20f80 RCX: 00007fe3eeb01b29
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000000
RBP: 00007fe3eeb4d47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe3eec20f80 R15: 00007ffc0b5c2948
</TASK>
rcu: rcu_preempt kthread starved for 10467 jiffies! g49977 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:27000 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1884
rcu_gp_fqs_loop+0x2af/0xf70 kernel/rcu/tree.c:1959
rcu_gp_kthread+0xa4/0x360 kernel/rcu/tree.c:2132
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
NMI backtrace for cpu 1
CPU: 1 PID: 11093 Comm: syz-executor.1 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_check_gp_kthread_starvation+0x1d2/0x240 kernel/rcu/tree_stall.h:481
print_other_cpu_stall+0x137a/0x14d0 kernel/rcu/tree_stall.h:586
check_cpu_stall kernel/rcu/tree_stall.h:729 [inline]
rcu_pending kernel/rcu/tree.c:3911 [inline]
rcu_sched_clock_irq+0x94f/0x1770 kernel/rcu/tree.c:2606
update_process_times+0x196/0x200 kernel/time/timer.c:1788
tick_sched_handle kernel/time/tick-sched.c:237 [inline]
tick_sched_timer+0x22d/0x3c0 kernel/time/tick-sched.c:1441
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x55b/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:csd_lock_wait kernel/smp.c:440 [inline]
RIP: 0010:smp_call_function_many_cond+0xa93/0xd90 kernel/smp.c:969
Code: 04 03 84 c0 0f 85 84 00 00 00 45 8b 7d 00 44 89 fe 83 e6 01 31 ff e8 1c b9 0b 00 41 83 e7 01 75 07 e8 b1 b5 0b 00 eb 41 f3 90 <48> b8 00 00 00 00 00 fc ff df 0f b6 04 03 84 c0 75 11 41 f7 45 00
RSP: 0018:ffffc90004c3f980 EFLAGS: 00000246
RAX: ffffffff81744b14 RBX: 1ffff11017348379 RCX: 0000000000040000
RDX: ffffc9000ed4e000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90004c3faa8 R08: ffffffff81744ae4 R09: fffffbfff1f7a655
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff8880b9a41bc8 R14: ffff8880b9b3a740 R15: 0000000000000001
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1135
kill_bdev block/bdev.c:76 [inline]
set_blocksize+0x2f3/0x370 block/bdev.c:157
sb_set_blocksize+0x45/0xe0 block/bdev.c:166
ntfs_fill_super+0x17b2/0x2e20 fs/ntfs/super.c:2811
mount_bdev+0x2c9/0x3f0 fs/super.c:1378
legacy_get_tree+0xeb/0x180 fs/fs_context.c:610
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1834e5d22a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f18333dcee8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f18333dcf80 RCX: 00007f1834e5d22a
RDX: 000000002001f6c0 RSI: 000000002001f640 RDI: 00007f18333dcf40
RBP: 000000002001f6c0 R08: 00007f18333dcf80 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000202 R12: 000000002001f640
R13: 00007f18333dcf40 R14: 000000000001f635 R15: 0000000020000080
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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