[v6.1] INFO: rcu detected stall in sys_clock_settime

1 view
Skip to first unread message

syzbot

unread,
Apr 11, 2023, 1:26:00 PM4/11/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10a925adc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9affea290775ea7
dashboard link: https://syzkaller.appspot.com/bug?extid=b416cb5da4c449ea0d75
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/6fe9097a8f09/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9df5aa0f6266/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84127c4bde2b/bzImage-543aff19.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-...D } 2690 jiffies s: 34049 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 16027 Comm: syz-executor.1 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xc5/0x130 kernel/locking/spinlock.c:194
Code: f7 e8 8f f5 57 f7 48 c7 44 24 20 00 00 00 00 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 f2 f4 57 f7 f6 44 24 21 02 75 4e <41> f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 e8 f7 12 d6 f6 65 8b
RSP: 0018:ffffc900001e0ca0 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff9200003c198 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff91c91378
RBP: ffffc900001e0d28 R08: dffffc0000000000 R09: fffffbfff2392270
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff9200003c194 R14: ffffc900001e0cc0 R15: 0000000000000046
FS: 00007f6dd9a6c700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6dd8da8000 CR3: 00000000205ec000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
debug_hrtimer_deactivate kernel/time/hrtimer.c:425 [inline]
debug_deactivate+0x1d/0x280 kernel/time/hrtimer.c:481
__run_hrtimer kernel/time/hrtimer.c:1653 [inline]
__hrtimer_run_queues+0x334/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1096 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1113
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1107
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [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 f2 f4 57 f7 f6 44 24 21 02 75 4e 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> f7 12 d6 f6 65 8b 05 38 b6 7a 75 85 c0 74 3f 48 c7 04 24 0e 36
RSP: 0018:ffffc900171d7b60 EFLAGS: 00000206
RAX: 5ab095dbc140e600 RBX: 1ffff92002e3af70 RCX: ffffffff816a0f5a
RDX: dffffc0000000000 RSI: ffffffff8aebc5e0 RDI: 0000000000000001
RBP: ffffc900171d7bf0 R08: dffffc0000000000 R09: fffffbfff204e031
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92002e3af6c R14: ffffc900171d7b80 R15: 0000000000000246
clock_was_set+0x179/0x900 kernel/time/hrtimer.c:970
do_settimeofday64+0x673/0x7e0 kernel/time/timekeeping.c:1345
__do_sys_clock_settime kernel/time/posix-timers.c:1088 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1076 [inline]
__x64_sys_clock_settime+0x232/0x270 kernel/time/posix-timers.c:1076
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+0x63/0xcd
RIP: 0033:0x7f6dd8c8c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6dd9a6c168 EFLAGS: 00000246 ORIG_RAX: 00000000000000e3
RAX: ffffffffffffffda RBX: 00007f6dd8dabf80 RCX: 00007f6dd8c8c169
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000000
RBP: 00007f6dd8ce7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc03ff042f R14: 00007f6dd9a6c300 R15: 0000000000022000
</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.
Reply all
Reply to author
Forward
0 new messages