INFO: rcu detected stall in x86_emulate_instruction

7 views
Skip to first unread message

syzbot

unread,
Sep 10, 2018, 1:21:06 PM9/10/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 11da3a7f84f1 Linux 4.19-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ec2869400000
kernel config: https://syzkaller.appspot.com/x/.config?x=9917ff4b798e1a1e
dashboard link: https://syzkaller.appspot.com/bug?extid=559d35a6fb3e23728fe2
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [h...@zytor.com k...@vger.kernel.org
linux-...@vger.kernel.org mi...@redhat.com pbon...@redhat.com
rkr...@redhat.com tg...@linutronix.de x...@kernel.org]

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+559d35...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: (detected by 0, t=10502 jiffies, g=50633, q=38)
rcu: All QSes seen, last rcu_preempt kthread activity 10503
(4294995116-4294984613), jiffies_till_next_fqs=1, root ->qsmask 0x0
syz-executor7 R running task 21216 18677 5362 0x00000000
Call Trace:
<IRQ>
sched_show_task.cold.83+0x2b6/0x30a kernel/sched/core.c:5296
print_other_cpu_stall.cold.79+0xa83/0xba5 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+0xafc/0x1990 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+0x41c/0x10d0 kernel/time/hrtimer.c:1460
hrtimer_interrupt+0x313/0x780 kernel/time/hrtimer.c:1518
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1029 [inline]
smp_apic_timer_interrupt+0x1a1/0x760 arch/x86/kernel/apic/apic.c:1054
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:864
</IRQ>
RIP: 0010:init_emulate_ctxt+0xac/0x5b0 arch/x86/kvm/x86.c:5802
Code: 72 00 4c 8b 2d a5 ee 24 09 48 8d 83 e0 38 00 00 48 89 85 30 ff ff ff
49 8d bd d8 00 00 00 48 89 f8 48 c1 e8 03 42 80 3c 38 00 <0f> 85 7b 04 00
00 49 8d 56 c0 49 8b 85 d8 00 00 00 48 89 df 49 8d
RSP: 0018:ffff880187026c60 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff122e01b RBX: ffff88018af60440 RCX: ffffc90005069000
RDX: 0000000000040000 RSI: ffffffff810c3ee4 RDI: ffffffff891700d8
RBP: ffff880187026d40 R08: ffff880193b1c140 R09: fffff5200035c6d5
R10: fffff5200035c6d5 R11: ffffc90001ae36ab R12: 1ffff10030e04d8f
R13: ffffffff89170000 R14: ffff880187026d18 R15: dffffc0000000000
x86_emulate_instruction+0x647/0x1fc0 arch/x86/kvm/x86.c:6162
kvm_mmu_page_fault+0x396/0x1b30 arch/x86/kvm/mmu.c:5280
handle_ept_violation+0x29e/0x6a0 arch/x86/kvm/vmx.c:7679
vmx_handle_exit+0x2f7/0x17e0 arch/x86/kvm/vmx.c:10115
vcpu_enter_guest+0x14a9/0x62e0 arch/x86/kvm/x86.c:7648
vcpu_run arch/x86/kvm/x86.c:7711 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7888
kvm_vcpu_ioctl+0x72b/0x1150 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2590
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: fd b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fd7769d1c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fd7769d26d4 RCX: 0000000000457099
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006
RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf730 R14: 00000000004c59b9 R15: 0000000000000000
rcu: rcu_preempt kthread starved for 10603 jiffies! g50633 f0x2
RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt R running task 23064 10 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
schedule+0xfe/0x460 kernel/sched/core.c:3517
schedule_timeout+0x140/0x260 kernel/time/timer.c:1804
rcu_gp_kthread+0x9d9/0x2310 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.

Dmitry Vyukov

unread,
Sep 11, 2018, 5:32:26 AM9/11/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
#syz dup: INFO: rcu detected stall in kvm_vcpu_ioctl
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/000000000000f58263057587949b%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages