linux-kernel - Re: [perf] more perf_fuzzer memory corruption

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: <20140417094815.GA9348@gmail.com>
Date:	Thu, 17 Apr 2014 11:48:15 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [perf] more perf_fuzzer memory corruption


* Vince Weaver <vincent.weaver@...ne.edu> wrote:

> On Wed, 16 Apr 2014, Vince Weaver wrote:
> 
> > On Wed, 16 Apr 2014, Peter Zijlstra wrote:
> > 
> > > Does the below make any difference? I've only ran it through some light
> > > testing to make sure it didn't insta-explode on running.
> > > 
> > > (perf stat make -j64 -s in fact)
> > 
> > I'm running with your patch now and so far so good.
> 
> spoke too soon, just got this with your patch applied
> (I wasn't running ftrace so no trace with this one):

Is there some place where I can pick up the latestest of your fuzzer?

PeterZ has trouble reproducing the corruption locally - I'd like to 
run it too, maybe I have hardware that triggers it more readily.

Plus it would be nice to get your latest .config as well, that you are 
using to generate this crash. (You can send it in private mail as well 
if you wish.)

Thanks,

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