INFO: rcu detected stall in vmx_vcpu_load

4 views
Skip to first unread message

syzbot

unread,
Sep 3, 2018, 6:51:03 PM9/3/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 58c3f14f86c9 Merge tag 'riscv-for-linus-4.19-rc2' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11e7487c400000
kernel config: https://syzkaller.appspot.com/x/.config?x=531a917630d2a492
dashboard link: https://syzkaller.appspot.com/bug?extid=f6154bbb256ad0eb74c1
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [adob...@gmail.com ak...@linux-foundation.org
fred...@kernel.org linux-...@vger.kernel.org mi...@kernel.org
tg...@linutronix.de]

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

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

rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
rcu: (detected by 0, t=105002 jiffies, g=89793, q=195)
rcu: All QSes seen, last rcu_sched kthread activity 105002
(4295067669-4294962667), jiffies_till_next_fqs=3, root ->qsmask 0x0
syz-executor5 R running task 24488 9936 4748 0x00000008
Call Trace:
<IRQ>
sched_show_task.cold.85+0x273/0x2d5 kernel/sched/core.c:5296
print_other_cpu_stall.cold.79+0x8e0/0x91d kernel/rcu/tree.c:1430
check_cpu_stall kernel/rcu/tree.c:1557 [inline]
__rcu_pending kernel/rcu/tree.c:3276 [inline]
rcu_pending kernel/rcu/tree.c:3319 [inline]
rcu_check_callbacks+0x986/0x15a0 kernel/rcu/tree.c:2665
update_process_times+0x2d/0x70 kernel/time/timer.c:1636
tick_sched_handle+0x9f/0x180 kernel/time/tick-sched.c:164
tick_sched_timer+0x45/0x130 kernel/time/tick-sched.c:1274
__run_hrtimer kernel/time/hrtimer.c:1398 [inline]
__hrtimer_run_queues+0x3eb/0xff0 kernel/time/hrtimer.c:1460
hrtimer_interrupt+0x2f3/0x750 kernel/time/hrtimer.c:1518
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1029 [inline]
smp_apic_timer_interrupt+0x16d/0x6a0 arch/x86/kernel/apic/apic.c:1054
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:864
</IRQ>
RIP: 0010:csd_lock_wait kernel/smp.c:108 [inline]
RIP: 0010:smp_call_function_single+0x3f5/0x5c0 kernel/smp.c:302
Code: 48 89 44 24 28 e8 9b 3b 0c 00 45 85 e4 74 67 48 8b 44 24 28 48 83 c3
18 49 89 c4 e8 75 3a 0c 00 f3 90 48 89 d8 41 c6 04 24 04 <48> c1 e8 03 42
0f b6 04 28 84 c0 74 08 3c 03 0f 8e 35 01 00 00 41
RSP: 0018:ffff8801cfb8f3a0 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff8801cfb8f418 RBX: ffff8801cfb8f418 RCX: ffffffff8170865c
RDX: 0000000000000000 RSI: ffffffff8170860b RDI: 0000000000000005
RBP: ffff8801cfb8f4f0 R08: ffff8801bcb92140 R09: ffffed003b625b98
R10: ffffed003b625b98 R11: ffff8801db12dcc7 R12: ffffed0039f71e90
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000001
loaded_vmcs_clear arch/x86/kvm/vmx.c:2218 [inline]
vmx_vcpu_load+0x873/0xfe0 arch/x86/kvm/vmx.c:3062
kvm_arch_vcpu_load+0x22b/0x940 arch/x86/kvm/x86.c:3106
vcpu_load+0x32/0x40 arch/x86/kvm/../../../virt/kvm/kvm_main.c:164
kvm_unload_vcpu_mmu arch/x86/kvm/x86.c:8852 [inline]
kvm_free_vcpus arch/x86/kvm/x86.c:8867 [inline]
kvm_arch_destroy_vm+0x1f9/0x7c0 arch/x86/kvm/x86.c:8967
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:752 [inline]
kvm_put_kvm+0x73f/0x1060 arch/x86/kvm/../../../virt/kvm/kvm_main.c:773
kvm_vcpu_release+0x7b/0xa0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2407
__fput+0x38a/0xa40 fs/file_table.c:278
____fput+0x15/0x20 fs/file_table.c:309
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x318/0x380 arch/x86/entry/common.c:166
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x410c41
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 34 19 00 00 c3 48
83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48
89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffc6fee9a70 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 000000000000000b RCX: 0000000000410c41
RDX: 0000000000000000 RSI: 00000000007305f0 RDI: 000000000000000a
RBP: 0000000000000000 R08: ffffffffffffffff R09: ffffffffffffffff
R10: 00007ffc6fee99a0 R11: 0000000000000293 R12: 0000000000000009
R13: 00000000000485c6 R14: 0000000000000052 R15: badc0ffeebadface
rcu: rcu_sched kthread starved for 105002 jiffies! g89793 f0x2
RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_sched R running task 23480 10 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x87c/0x1df0 kernel/sched/core.c:3473
schedule+0xfb/0x450 kernel/sched/core.c:3517
schedule_timeout+0x140/0x260 kernel/time/timer.c:1804
rcu_gp_kthread+0x743/0x1d20 kernel/rcu/tree.c:2194
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Feb 26, 2019, 4:42:06 PM2/26/19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages