From: Borislav Petkov <bp@alien8.de>
To: George Kennedy <george.kennedy@oracle.com>
Cc: joro@8bytes.org, pbonzini@redhat.com, mingo@redhat.com,
hpa@zytor.com, kvm@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: kernel BUG at arch/x86/kvm/x86.c:361! on AMD CPU
Date: Wed, 12 Jun 2019 21:51:52 +0200 [thread overview]
Message-ID: <20190612195152.GQ32652@zn.tnic> (raw)
In-Reply-To: <af0054d1-1fc8-c106-b503-ca91da5a6fee@oracle.com>
On Wed, Jun 12, 2019 at 02:45:34PM -0400, George Kennedy wrote:
> The crash can still be reproduced with VM running Upstream 5.2.0-rc4
That's clear.
> and host running Ubuntu on AMD CPU.
That's the important question: why can't I trigger it with 5.2.0-rc4+ as
the host and you can with the ubuntu kernel 4.15 or so. I.e., what changed
upstream or does the ubuntu kernel have out-of-tree stuff?
Maybe kvm folks would have a better idea. That kvm_spurious_fault thing
is for:
/*
* Hardware virtualization extension instructions may fault if a
* reboot turns off virtualization while processes are running.
* Trap the fault and ignore the instruction if that happens.
*/
asmlinkage void kvm_spurious_fault(void);
but you're not rebooting...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-06-12 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37952f51-7687-672c-45d9-92ba418c9133@oracle.com>
2019-06-12 16:12 ` kernel BUG at arch/x86/kvm/x86.c:361! on AMD CPU Borislav Petkov
[not found] ` <af0054d1-1fc8-c106-b503-ca91da5a6fee@oracle.com>
2019-06-12 19:51 ` Borislav Petkov [this message]
2019-06-12 20:54 ` Sean Christopherson
2019-06-13 7:18 ` Borislav Petkov
[not found] ` <df80299b-8e1f-f48b-a26b-c163b4018d01@oracle.com>
2019-06-18 17:51 ` Borislav Petkov
2019-06-18 18:01 ` Dmitry Vyukov
2019-06-18 18:27 ` Borislav Petkov
2019-06-18 19:17 ` Paolo Bonzini
2019-06-18 19:34 ` George Kennedy
2019-06-23 13:15 ` 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=20190612195152.GQ32652@zn.tnic \
--to=bp@alien8.de \
--cc=george.kennedy@oracle.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzkaller@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).