From: Borislav Petkov <bp@alien8.de>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
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: Thu, 13 Jun 2019 09:18:05 +0200 [thread overview]
Message-ID: <20190613071805.GA11598@zn.tnic> (raw)
In-Reply-To: <20190612205430.GA26320@linux.intel.com>
On Wed, Jun 12, 2019 at 01:54:30PM -0700, Sean Christopherson wrote:
> The reboot thing is a red-herring. The ____kvm_handle_fault_on_reboot()
> macro suppresses faults that occur on VMX and SVM instructions while the
> kernel is rebooting (CPUs need to leave VMX/SVM mode to recognize INIT),
> i.e. kvm_spurious_fault() is reached when a VMX or SVM instruction faults
> and we're *not* rebooting.
>
> TL;DR: an SVM instruction is faulting unexpectedly.
Aha, thx!
And there are a couple of places in svm_vcpu_run() which can cause that:
[ 135.498208] Call Trace:
[ 135.498594] svm_vcpu_run+0xa83/0x20e0
George, can you objdump the area around offset 0xa83 within svm_vcpu_run
of the guest kernel?
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-06-13 16:37 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
2019-06-12 20:54 ` Sean Christopherson
2019-06-13 7:18 ` Borislav Petkov [this message]
[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=20190613071805.GA11598@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=sean.j.christopherson@intel.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).