From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209845] ignore_msrs kernel NULL pointer dereference since 12bc2132b15e0a969b3f455d90a5f215ef239eff
Date: Sun, 25 Oct 2020 16:24:27 +0000 [thread overview]
Message-ID: <bug-209845-28872-a03GDh3XC4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209845-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209845
--- Comment #1 from peterx@redhat.com ---
On Sun, Oct 25, 2020 at 11:28:21AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=209845
>
> Bug ID: 209845
> Summary: ignore_msrs kernel NULL pointer dereference since
> 12bc2132b15e0a969b3f455d90a5f215ef239eff
> Product: Virtualization
> Version: unspecified
> Kernel Version: 5.9
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: kvm
> Assignee: virtualization_kvm@kernel-bugs.osdl.org
> Reporter: kernel-bugs@steffen.cc
> Regression: No
>
> Created attachment 293183
> --> https://bugzilla.kernel.org/attachment.cgi?id=293183&action=edit
> dmesg section
>
> Since commit 12bc2132b15e0a969b3f455d90a5f215ef239eff kvm crashes with a null
> pointer dereference when ignore_msrs is set (log in attachement)
>
> Hardware: AMD Ryzen 3700x
kvm_msr_ignored_check() should consider vcpu null case for kvm vm get msr
features.. I'll post a fix soon, probably with a selftest too. Thanks,
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-10-25 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 11:28 [Bug 209845] New: ignore_msrs kernel NULL pointer dereference since 12bc2132b15e0a969b3f455d90a5f215ef239eff bugzilla-daemon
2020-10-25 16:24 ` Peter Xu
2020-10-25 16:24 ` 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-209845-28872-a03GDh3XC4@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