linux-kernel - Re: GPF in intel_pmu_lbr_reset() with qemu -cpu host

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]

Date:	Sat, 22 Mar 2014 23:00:24 +0100
From:	Peter Wu <peter@...ensteyn.nl>
To:	Gleb Natapov <gleb@...nel.org>
Cc:	Venkatesh Srinivas <venkateshs@...gle.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andi Kleen <ak@...ux.intel.com>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org,
	Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: GPF in intel_pmu_lbr_reset() with qemu -cpu host

On Saturday 22 March 2014 14:27:59 Gleb Natapov wrote:
> > but now I have a NULL dereference (in rapl_pmu_init). Previously, when
> > `-cpu SandyBridge` was passed to qemu, it would show this:
> > 
> >     [    0.016995] Performance Events: unsupported p6 CPU model 42 no PMU driver, software events only.
> > 
> > The same NULL pointer deref would be visible (slightly different
> > addresses, but the Code lines are equal). With `-host`, the NULL deref
> > with `-cpu host` contains:
> > 
> >     [    0.016445] Performance Events: 16-deep LBR, IvyBridge events, Intel PMU driver.
> > 
> > Full dmesg below.
> > 
> I am confused. Do you see crash now with -cpu SandyBridge and -cpu host, or -cpu host only?

The RAPL crash is seen with both SandyBridge and host, I mentioned SB
because that environment should be more constant than "host" (which
depends on the CPU you have on, well, the host).

Peter

--
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/