linux-kernel - Re: [KVM] BUG: unable to handle kernel NULL pointer dereference at 00000000000002b0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5332F668.8080601@redhat.com>
Date:	Wed, 26 Mar 2014 16:46:48 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
CC:	LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [KVM] BUG: unable to handle kernel NULL pointer dereference at
 00000000000002b0

Il 26/03/2014 15:57, Fengguang Wu ha scritto:
>>> > >
>>> > >git://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
>>> > >commit 93c4adc7afedf9b0ec190066d45b6d67db5270da ("KVM: x86: handle missing MPX in nested virtualization")
>> >
>> > Ouch.  Out of curiosity is this on Skylake prototypes, or is it also
>> > visible on some released silicon?
> Paolo, the problem shows up in a Sandybridge-EX and an Ivybridge-EX.

What does that mean in terms of commercial names?  I tested on Sandy 
Bridge Xeon E5.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/