From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203923] Running a nested freedos on AMD Athlon i686-pae results in NULL pointer dereference in L0 (kvm_mmu_load)
Date: Wed, 01 Apr 2020 17:09:40 +0000 [thread overview]
Message-ID: <bug-203923-28872-IwN1VvtyyK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203923-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203923
--- Comment #9 from Jiri Palecek (jpalecek@web.de) ---
(In reply to Anders Kaseorg from comment #8)
> The second patch was committed as v5.4-rc1~138^2~6.
>
> I found this while staring at a similar-looking kvm_mmu_load NULL
> dereference on the hardware kernel while starting a nested VM on an AMD
> Ryzen 7 1800X, kernel 5.4.28. Should I try to expand this into a full
> report, or does your original recipe still reproduce?
Hi. I was going to say your problem was likely to be something else, because
that original problem got fixed, and anyway all of my problems with kvm were
specifically related to 32bit. However then I tried it for myself and it's
still broken, albeit with a different error message. Oh well...
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-04-01 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 15:01 [Bug 203923] New: Running a nested freedos results in NULL pointer dereference in L0 (kvm_mmu_load) bugzilla-daemon
2019-06-18 15:03 ` [Bug 203923] Running a nested freedos on AMD Athlon i686-pae " bugzilla-daemon
2019-06-20 10:19 ` bugzilla-daemon
2019-06-20 13:57 ` bugzilla-daemon
2019-06-20 22:14 ` bugzilla-daemon
2019-06-22 22:49 ` bugzilla-daemon
2020-04-01 4:39 ` bugzilla-daemon
2020-04-01 17:09 ` bugzilla-daemon [this message]
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-203923-28872-IwN1VvtyyK@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).