INFO: rcu detected stall in kvm_vcpu_gfn_to_memslot
9 views
Skip to first unread message
syzbot
Sep 11, 2018, 2:12:05 AM9/11/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 3d0e7a9e00fd Merge tag 'md/4.19-rc2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e93b7a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=4e09176f2378405fe8bc
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [k...@vger.kernel.org linux-...@vger.kernel.org
pbon...@redhat.com rkr...@redhat.com]
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+4e0917...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (1 GPs behind) idle=1de/1/0x4000000000000002
softirq=68126/68129 fqs=0
rcu: (t=10500 jiffies g=93905 q=84)
rcu: rcu_preempt kthread starved for 10500 jiffies! g93905 f0x0
RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt I23064 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
NMI backtrace for cpu 0
CPU: 0 PID: 28034 Comm: syz-executor5 Not tainted 4.19.0-rc2+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b3/0x1ed lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:162 [inline]
rcu_dump_cpu_stacks+0x175/0x1c2 kernel/rcu/tree.c:1340
print_cpu_stall.cold.78+0x2d3/0x524 kernel/rcu/tree.c:1478
check_cpu_stall kernel/rcu/tree.c:1550 [inline]
__rcu_pending kernel/rcu/tree.c:3276 [inline]
rcu_pending kernel/rcu/tree.c:3319 [inline]
rcu_check_callbacks+0xfd9/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:debug_lockdep_rcu_enabled+0x2d/0x90 kernel/rcu/update.c:252
Code: 50 4a 31 8a 55 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 89 e5 48 c1
ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 04 <84> d2 75 4c 8b
15 59 89 c9 08 85 d2 74 3e 48 c7 c7 80 65 93 89 48
RSP: 0018:ffff8801a2da6a58 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000003 RBX: ffffc900152f8000 RCX: ffffc9000746b000
RDX: 0000000000000000 RSI: ffffffff8108c79c RDI: ffffffff8a314a50
RBP: ffff8801a2da6a58 R08: ffff8801a03f81c0 R09: fffff52002a602d5
R10: fffff52002a602d5 R11: ffffc900153016ab R12: 0000000000000002
R13: 0000000000000000 R14: ffff8801bc065200 R15: ffff8801a2da6bb0
srcu_read_lock_held include/linux/srcu.h:131 [inline]
__kvm_memslots include/linux/kvm_host.h:581 [inline]
kvm_vcpu_memslots include/linux/kvm_host.h:595 [inline]
kvm_vcpu_gfn_to_memslot+0x6b1/0x7f0
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1229
kvm_page_track_is_active+0x9a/0x1f0 arch/x86/kvm/page_track.c:156
page_fault_handle_page_track.part.93+0x1f/0x30 arch/x86/kvm/mmu.c:3885
page_fault_handle_page_track arch/x86/kvm/mmu.c:4046 [inline]
tdp_page_fault+0x54e/0xbe0 arch/x86/kvm/mmu.c:4045
kvm_mmu_page_fault+0x226/0x1ad0 arch/x86/kvm/mmu.c:5240
handle_ept_violation+0x29e/0x6a0 arch/x86/kvm/vmx.c:7679
vmx_handle_exit+0x2f7/0x17f0 arch/x86/kvm/vmx.c:10115
vcpu_enter_guest+0x14a9/0x62e0 arch/x86/kvm/x86.c:7630
vcpu_run arch/x86/kvm/x86.c:7693 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7870
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:00007f250a2e7c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f250a2e86d4 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
Sending NMI from CPU 0 to CPUs 1:
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.092
msecs
NMI backtrace for cpu 1
CPU: 1 PID: 28037 Comm: syz-executor0 Not tainted 4.19.0-rc2+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:check_kcov_mode kernel/kcov.c:67 [inline]
RIP: 0010:write_comp_data+0x16/0x70 kernel/kcov.c:122
Code: ff e8 5e ef c9 ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 65 4c
8b 04 25 40 ee 01 00 65 8b 05 ef 1e 83 7e a9 00 01 1f 00 <48> 89 e5 75 51
41 8b 80 d0 12 00 00 83 f8 03 75 45 49 8b 80 d8 12
RSP: 0018:ffff88019dd0f328 EFLAGS: 00000046
RAX: 0000000080000001 RBX: ffff88024c74c000 RCX: ffffffff81386beb
RDX: ffff88024c74c000 RSI: ffff8801cc74c000 RDI: 0000000000000006
RBP: ffff88019dd0f338 R08: ffff88018a850100 R09: 1ffffffff12b43cd
R10: ffffed003b5e4732 R11: ffff8801daf23993 R12: ffff8801cc74c000
R13: 0000000000000000 R14: ffff880189518480 R15: ffff880189518480
FS: 00007f1fd6891700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001cc74c000 CR4: 00000000001426e0
Call Trace:
__phys_addr+0x2b/0x120 arch/x86/mm/physaddr.c:19
build_cr3 arch/x86/include/asm/tlbflush.h:127 [inline]
__get_current_cr3_fast arch/x86/include/asm/mmu_context.h:331 [inline]
vmx_vcpu_run+0xb47/0x2700 arch/x86/kvm/vmx.c:10648
vcpu_run arch/x86/kvm/x86.c:7693 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7870
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:00007f1fd6890c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1fd68916d4 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
---
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 found the following crash on:
HEAD commit: 3d0e7a9e00fd Merge tag 'md/4.19-rc2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e93b7a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=4e09176f2378405fe8bc
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [k...@vger.kernel.org linux-...@vger.kernel.org
pbon...@redhat.com rkr...@redhat.com]
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+4e0917...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (1 GPs behind) idle=1de/1/0x4000000000000002
softirq=68126/68129 fqs=0
rcu: (t=10500 jiffies g=93905 q=84)
rcu: rcu_preempt kthread starved for 10500 jiffies! g93905 f0x0
RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt I23064 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
NMI backtrace for cpu 0
CPU: 0 PID: 28034 Comm: syz-executor5 Not tainted 4.19.0-rc2+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b3/0x1ed lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:162 [inline]
rcu_dump_cpu_stacks+0x175/0x1c2 kernel/rcu/tree.c:1340
print_cpu_stall.cold.78+0x2d3/0x524 kernel/rcu/tree.c:1478
check_cpu_stall kernel/rcu/tree.c:1550 [inline]
__rcu_pending kernel/rcu/tree.c:3276 [inline]
rcu_pending kernel/rcu/tree.c:3319 [inline]
rcu_check_callbacks+0xfd9/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:debug_lockdep_rcu_enabled+0x2d/0x90 kernel/rcu/update.c:252
Code: 50 4a 31 8a 55 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 89 e5 48 c1
ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 04 <84> d2 75 4c 8b
15 59 89 c9 08 85 d2 74 3e 48 c7 c7 80 65 93 89 48
RSP: 0018:ffff8801a2da6a58 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000003 RBX: ffffc900152f8000 RCX: ffffc9000746b000
RDX: 0000000000000000 RSI: ffffffff8108c79c RDI: ffffffff8a314a50
RBP: ffff8801a2da6a58 R08: ffff8801a03f81c0 R09: fffff52002a602d5
R10: fffff52002a602d5 R11: ffffc900153016ab R12: 0000000000000002
R13: 0000000000000000 R14: ffff8801bc065200 R15: ffff8801a2da6bb0
srcu_read_lock_held include/linux/srcu.h:131 [inline]
__kvm_memslots include/linux/kvm_host.h:581 [inline]
kvm_vcpu_memslots include/linux/kvm_host.h:595 [inline]
kvm_vcpu_gfn_to_memslot+0x6b1/0x7f0
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1229
kvm_page_track_is_active+0x9a/0x1f0 arch/x86/kvm/page_track.c:156
page_fault_handle_page_track.part.93+0x1f/0x30 arch/x86/kvm/mmu.c:3885
page_fault_handle_page_track arch/x86/kvm/mmu.c:4046 [inline]
tdp_page_fault+0x54e/0xbe0 arch/x86/kvm/mmu.c:4045
kvm_mmu_page_fault+0x226/0x1ad0 arch/x86/kvm/mmu.c:5240
handle_ept_violation+0x29e/0x6a0 arch/x86/kvm/vmx.c:7679
vmx_handle_exit+0x2f7/0x17f0 arch/x86/kvm/vmx.c:10115
vcpu_enter_guest+0x14a9/0x62e0 arch/x86/kvm/x86.c:7630
vcpu_run arch/x86/kvm/x86.c:7693 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7870
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:00007f250a2e7c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f250a2e86d4 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
Sending NMI from CPU 0 to CPUs 1:
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.092
msecs
NMI backtrace for cpu 1
CPU: 1 PID: 28037 Comm: syz-executor0 Not tainted 4.19.0-rc2+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:check_kcov_mode kernel/kcov.c:67 [inline]
RIP: 0010:write_comp_data+0x16/0x70 kernel/kcov.c:122
Code: ff e8 5e ef c9 ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 65 4c
8b 04 25 40 ee 01 00 65 8b 05 ef 1e 83 7e a9 00 01 1f 00 <48> 89 e5 75 51
41 8b 80 d0 12 00 00 83 f8 03 75 45 49 8b 80 d8 12
RSP: 0018:ffff88019dd0f328 EFLAGS: 00000046
RAX: 0000000080000001 RBX: ffff88024c74c000 RCX: ffffffff81386beb
RDX: ffff88024c74c000 RSI: ffff8801cc74c000 RDI: 0000000000000006
RBP: ffff88019dd0f338 R08: ffff88018a850100 R09: 1ffffffff12b43cd
R10: ffffed003b5e4732 R11: ffff8801daf23993 R12: ffff8801cc74c000
R13: 0000000000000000 R14: ffff880189518480 R15: ffff880189518480
FS: 00007f1fd6891700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001cc74c000 CR4: 00000000001426e0
Call Trace:
__phys_addr+0x2b/0x120 arch/x86/mm/physaddr.c:19
build_cr3 arch/x86/include/asm/tlbflush.h:127 [inline]
__get_current_cr3_fast arch/x86/include/asm/mmu_context.h:331 [inline]
vmx_vcpu_run+0xb47/0x2700 arch/x86/kvm/vmx.c:10648
vcpu_run arch/x86/kvm/x86.c:7693 [inline]
kvm_arch_vcpu_ioctl_run+0x375/0x16e0 arch/x86/kvm/x86.c:7870
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:00007f1fd6890c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1fd68916d4 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
---
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
Sep 11, 2018, 5:31:37 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/00000000000055d5090575925a76%40google.com.
> For more options, visit https://groups.google.com/d/optout.
> 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/00000000000055d5090575925a76%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages