linux-kernel - Re: perf: fuzzer causes lockup in x86_pmu_event

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:	Tue, 17 Mar 2015 11:00:44 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Jiri Olsa <jolsa@...hat.com>
cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: perf: fuzzer causes lockup in x86_pmu_event_init()

On Tue, 17 Mar 2015, Jiri Olsa wrote:

> > I'll start my test-machine fuzzing with this plus the infinite-interrupt 
> > fix and see what happens.  The machines do eventually trigger the issue
> > somwhat consistently but it can take up to a week before they hit it
> > so it's a tough one to test for.
> 
> I guess no news is good news in here..  ;-)

yes, with both the irq-storm patch plus your patch I've been fuzzing for 
over a week with no crashes.  (I'm only using your patch for the lockup 
problem, not Peter's).

There are other minor warnings that pop up as per usual, and if you fuzz 
with paranoid set to 1 you quickly crash with the uncore issue I reported 
a while back, but otherwise things seem really solid with the two patches 
I mentioned.

Of course that's what I always say just before things start crashing 
again, although right now I had to stop the fuzzing temporarily as somehow 
the fuzzer is leaking children for reasons I don't understand and I'm 
trying to debug.

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/