linux-kernel - Re: perf/tracepoint yet another lockup

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.10.1311131737100.5706@vincent-weaver-1.um.maine.edu>
Date:	Wed, 13 Nov 2013 17:39:33 -0500 (EST)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: perf/tracepoint yet another lockup

On Tue, 12 Nov 2013, Peter Zijlstra wrote:

> On Mon, Nov 11, 2013 at 05:28:21PM -0500, Vince Weaver wrote:
> > So are all tracepoints unsafe?  Or just a subset?
> 
> No, most should be fine. But finding the special ones seems interesting
> :/
> 
> Disabling them all for now sure seems like the safe option.

Update on this, it was a false positive.  It seems like the other crashes 
I was seeing were also caused by tracepoint 24, the fuzzer just found them 
via another code path I wasn't checking.

So from what I can tell the only troublesome tracepoint I've come across 
is the original irq_vectors/irq_work_exit problem.

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/