linux-kernel - Re: perf: fuzzer triggered trouble on AMD, maybe ibs related

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: <20151023221236.GG17308@twins.programming.kicks-ass.net>
Date:	Sat, 24 Oct 2015 00:12:36 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Stephane Eranian <eranian@...il.com>, rric@...nel.org
Subject: Re: perf: fuzzer triggered trouble on AMD, maybe ibs related

On Thu, Oct 22, 2015 at 12:46:53PM -0400, Vince Weaver wrote:
> Hello
> 
> I've been busy but finally had a chance to run perf_fuzzer on current git.
> I am running on an AMD A10 system (my traditional Haswell system is 
> otherwise occupied).
> 
> I got the following WARNING which was followed by an NMI storm which 
> eventually managed to confuse ext4 enough that my / partition was 
> remounted read-only? Very alarming.
> 
> This is in static void perf_ibs_start(struct perf_event *event, int flags)
> 
> 	if (WARN_ON_ONCE(!(hwc->state & PERF_HES_STOPPED)))
>                 return;

Hurm, its been a long while since I looked at the AMD IBS stuff. But
looking at it I would not be surprised if there's weird interaction
between the HES flags and IBS_flags.

But I'll have to look more careful..

> [  468.763231] Dazed and confused, but trying to continue
> [  468.794184] Uhhuh. NMI received for unknown reason 2d on CPU 2.
> [  468.794184] Do you have a strange power saving mode enabled?
> [  468.794184] Dazed and confused, but trying to continue
> [  473.190535] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> [  473.199631] sd 0:0:0:0: [sda] tag#2 CDB: Write(10) 2a 00 39 93 49 d0 00 00 18 00

This might just be the NMI storm starving a device interrupt.
--
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/