From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>,
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>
Cc: 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:36:19 +0200 [thread overview]
Message-ID: <a535733a-60a8-c763-49b5-d685be7e7002@redhat.com> (raw)
In-Reply-To: <CACT4Y+Z=9ArfCdGkc1ZgC56q-UGXVa=R1F5-CKFeg9-V-8iXxA@mail.gmail.com>
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.
Paolo
next prev parent reply other threads:[~2016-06-22 8:38 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 [this message]
2016-06-22 8:38 ` Dmitry Vyukov
2016-06-22 8:46 ` Paolo Bonzini
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=a535733a-60a8-c763-49b5-d685be7e7002@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®