linux-kernel - Re: x86_pmu_start WARN

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:	Thu, 13 Feb 2014 09:11:49 -0500 (EST)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Vince Weaver <vincent.weaver@...ne.edu>
cc:	Peter Zijlstra <peterz@...radead.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: x86_pmu_start WARN_ON.

On Wed, 12 Feb 2014, Vince Weaver wrote:

> On Tue, 11 Feb 2014, Peter Zijlstra wrote:
> > 
> > I'll see if I can run through the reproduction case by hand.
> 
> I've come up with an even simpler test case with all of the extraneous 
> settings removed.  Included below.
> 
> It is triggered in this case when you have:
> 
>   An event group of breakpoint, cycles, branches
>   An event of instructions with precise=1
>   A tracepoint
> 
> and then you close the tracepoint.

and for what it's worth, it's the cycles event (type=0 config=0) that's 
causing the WARN_ON.

It looks like I'm going to have to resort to sprinkling the code with 
printk()s to solve this one.

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