From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Gleb Natapov <gleb@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>, KVM list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
mtosatti@redhat.com, yoshikawa_takuya_b1@lab.ntt.co.jp,
guangrong.xiao@linux.intel.com,
Eric Northup <digitaleric@google.com>,
Andrew Honig <ahonig@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Eric Dumazet <edumazet@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: kvm: GPF in kvm_lapic_latched_init
Date: Wed, 22 Jun 2016 10:46:26 +0200 [thread overview]
Message-ID: <e5157c0e-d821-0d4a-9ec5-b681de6c44b1@redhat.com> (raw)
In-Reply-To: <CACT4Y+Yh5ZEFL_rOkThU_orQMpGVKQ3swU+7RmNjsUw+-aEEQA@mail.gmail.com>
On 22/06/2016 10:38, Dmitry Vyukov wrote:
> On Wed, Jun 22, 2016 at 10:36 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 22/06/2016 10:20, Dmitry Vyukov wrote:
>>>>>>> All crashes suggest that apic is NULL.
>>>>>>>
>>>>>>> On commit b06f3a168cdcd80026276898fd1fee443ef25743 (Jan 6).
>>>
>>> Ping. Just hit it again on 67016f6cdfd079e632bbc49e33178b2d558c120a (Jun 20):
>>
>> This might have been the same bug you reported yesterday in kvm_set_cr8.
>> I've sent a patch to fix static keys.
>
> Then it is probably the same as the following one as well?
Not 100% sure, can you send the reproducer?
Paolo
> WARNING: CPU: 3 PID: 23379 at kernel/sched/core.c:2583[< none
> >] preempt_notifier_register+0x2b/0x120 kernel/sched/core.c:2583
> registering preempt_notifier while notifiers disabled
> Modules linked in:
> CPU: 3 PID: 23379 Comm: syz-executor Not tainted 4.7.0-rc4+ #2
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> ffffffff880b58e0 ffff88003a79fa60 ffffffff82cc62cf ffffffff81495e98
> fffffbfff1016b1c ffff88003a79fad8 0000000000000000 ffffffff86ca0220
> ffffffff813ed78b 0000000000000009 ffff88003a79faa8 ffffffff8136d27f
> Call Trace:
> [< inline >] __dump_stack lib/dump_stack.c:15
> [<ffffffff82cc62cf>] dump_stack+0x12e/0x18f lib/dump_stack.c:51
> [<ffffffff8136d27f>] __warn+0x19f/0x1e0 kernel/panic.c:516
> [<ffffffff8136d36c>] warn_slowpath_fmt+0xac/0xd0 kernel/panic.c:531
> [<ffffffff813ed78b>] preempt_notifier_register+0x2b/0x120
> kernel/sched/core.c:2583
> [<ffffffff81067d96>] vcpu_load+0x46/0x70
> arch/x86/kvm/../../../virt/kvm/kvm_main.c:146
> [<ffffffff810b933f>] kvm_arch_vcpu_setup+0x1f/0x60 arch/x86/kvm/x86.c:7390
> [< inline >] kvm_vm_ioctl_create_vcpu
> arch/x86/kvm/../../../virt/kvm/kvm_main.c:2355
> [<ffffffff8106b9f2>] kvm_vm_ioctl+0x582/0x10d0
> arch/x86/kvm/../../../virt/kvm/kvm_main.c:2839
> [< inline >] vfs_ioctl fs/ioctl.c:43
> [<ffffffff818510bc>] do_vfs_ioctl+0x18c/0xff0 fs/ioctl.c:674
> [< inline >] SYSC_ioctl fs/ioctl.c:689
> [<ffffffff81851faf>] SyS_ioctl+0x8f/0xc0 fs/ioctl.c:680
> [<ffffffff86a97000>] entry_SYSCALL_64_fastpath+0x23/0xc1
> arch/x86/entry/entry_64.S:207
> ---[ end trace c0e5c1ad551a4947 ]---
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-06-22 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:42 Dmitry Vyukov
2016-01-15 17:12 ` Dmitry Vyukov
2016-01-18 9:57 ` Xiao Guangrong
2016-01-18 10:11 ` Dmitry Vyukov
2016-06-22 8:20 ` Dmitry Vyukov
2016-06-22 8:36 ` Paolo Bonzini
2016-06-22 8:38 ` Dmitry Vyukov
2016-06-22 8:46 ` Paolo Bonzini [this message]
2016-06-22 9:56 ` Dmitry Vyukov
2016-01-15 19:59 ` Jeff Merkey
2016-01-15 20:09 ` Dmitry Vyukov
2016-01-15 20:54 ` Jeff Merkey
2016-05-31 10:35 ` Paolo Bonzini
2016-06-01 7:59 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5157c0e-d821-0d4a-9ec5-b681de6c44b1@redhat.com \
--to=pbonzini@redhat.com \
--cc=ahonig@google.com \
--cc=digitaleric@google.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=gleb@kernel.org \
--cc=glider@google.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kcc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®