[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1404161326380.19325@vincent-weaver-1.um.maine.edu>
Date: Wed, 16 Apr 2014 13:30:06 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Peter Zijlstra <peterz@...radead.org>
cc: Vince Weaver <vincent.weaver@...ne.edu>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [perf] more perf_fuzzer memory corruption
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.
Unfortunately the problem isn't repeatable, but it usually shows up within
an hour or so of fuzzing (although there's possibly a 2nd unrelated bug
that also shows up sometimes).
If you want to try running the fuzzer on your machine too just do:
git clone https://github.com/deater/perf_event_tests.git
cd fuzzer
make
and then try running the "./fast_repro98.sh" script, as that's the forking
workload I've been using when tracking this issue.
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/
Powered by blists - more mailing lists