From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 210695] error: kvm run failed Invalid argument
Date: Thu, 17 Dec 2020 19:54:15 +0000 [thread overview]
Message-ID: <bug-210695-28872-ZDrKfe6vd4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210695-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210695
--- Comment #7 from Sean Christopherson (seanjc@google.com) ---
Finally figured it out. When KVM uses PAE shadow paging, the PDPTRs are
effectively skipped when walking the shadow tables because a bad PDPTR will be
detected much earlier and KVM essentially hardcodes the PDPTRs. As a result,
the corresponding SPTE isn't filled by get_walk() as it never "sees" the SPTE
for the PDTPR. The refactored get_mmio_spte() doesn't account for this and
checks the PDPTR SPTE array value. This reads uninitialized stack data, and in
your case, this yields the garbage value '0x80000b0e' that causes things to
explode (my system gets '0' most/all of the time).
I'll get a patch out later today, it's a bit of a mess....
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-12-17 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 0:11 [Bug 210695] New: error: kvm run failed Invalid argument bugzilla-daemon
2020-12-15 0:13 ` [Bug 210695] " bugzilla-daemon
2020-12-16 2:03 ` bugzilla-daemon
2020-12-16 2:28 ` bugzilla-daemon
2020-12-16 2:57 ` bugzilla-daemon
2020-12-16 20:49 ` bugzilla-daemon
2020-12-16 23:08 ` bugzilla-daemon
2020-12-16 23:14 ` bugzilla-daemon
2020-12-17 19:54 ` bugzilla-daemon [this message]
2020-12-18 3:10 ` bugzilla-daemon
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=bug-210695-28872-ZDrKfe6vd4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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).