linux-kernel - Re: perf: fuzzer: spinlock hang

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160817154049.GU30192@twins.programming.kicks-ass.net>
Date:	Wed, 17 Aug 2016 17:40:49 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: perf: fuzzer: spinlock hang

On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
> 
> So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the 
> system finally locked up permanently.
> 
> It looks like some sort of spinlock error.
> The logs continued being spammed with this stuff overnight until I 
> finally put it out of its misery, but I think just the beginning here
> is the relevant part.

That sadly looks vaguely familiar... I think its the point where I gave
up chasing bugs last year, because I was going soft in the head staring
at this stuff for several months non-stop.

It taking several hours to reproduce didn't help.

I suspect its something iffy with the Intel driver, because I could
never trigger it on AMD, but of course, no guarantees ...

I'll try and find some time again to chase this down once Alexander
sorts that AUX issue.