mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jet Chen <jet.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [KVM] BUG: unable to handle kernel NULL pointer dereference at 00000000000002b0
Date: Mon, 28 Apr 2014 13:34:17 +0200	[thread overview]
Message-ID: <535E3CB9.9070709@redhat.com> (raw)
In-Reply-To: <535E254A.4020500@intel.com>

Il 28/04/2014 11:54, Jet Chen ha scritto:
>>> >> We noticed the below kernel BUG on
>>> >>
>>> >> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> >
>> > What commit?
>> >
> This one,
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 93c4adc7afedf9b0ec190066d45b6d67db5270da
> Author:     Paolo Bonzini <pbonzini@redhat.com>
> AuthorDate: Wed Mar 5 23:19:52 2014 +0100
> Commit:     Paolo Bonzini <pbonzini@redhat.com>
> CommitDate: Mon Mar 17 12:21:39 2014 +0100
>
>       KVM: x86: handle missing MPX in nested virtualization
>
>
> BTW, the same issue has been reported by Fengguang last month.
>
> https://lkml.org/lkml/2014/3/26/200

It should have been fixed already by commit 920c83778569 (KVM: vmx: fix 
MPX detection, 2014-03-26).  That's why I was confused, I thought it was 
for a recent commit on Linus's master branch.

Paolo

  reply	other threads:[~2014-04-28 11:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  7:49 Jet Chen
2014-04-28  9:33 ` Paolo Bonzini
2014-04-28  9:54   ` Jet Chen
2014-04-28 11:34     ` Paolo Bonzini [this message]
2014-04-28 13:52       ` Jet Chen
  -- strict thread matches above, loose matches on Subject: below --
2014-03-26 14:40 Fengguang Wu
2014-03-26 14:50 ` Paolo Bonzini
2014-03-26 14:57   ` Fengguang Wu
2014-03-26 15:46     ` Paolo Bonzini
2014-03-27  2:56       ` Fengguang Wu
2014-03-26 14:52 ` Paolo Bonzini

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=535E3CB9.9070709@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=jet.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.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

Powered by JetHome