lkml.org 
[lkml]   [2014]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [perf] more perf_fuzzer memory corruption
On Thu, 17 Apr 2014, Ingo Molnar wrote:

>
> * Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Thu, Apr 17, 2014 at 11:48:15AM +0200, Ingo Molnar wrote:
> > > 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.
> >
> > From a few emails up:
> >
> > "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."

I have to admit the slab corruption message is a new development with
3.15-rc1.

I've been trying to track a possibly-the-same (but harder to debug)
memory corruption issue for a while now.

I can trigger this type of error easily on both a core2 and haswell
machine.

I have a few more test machines I can run, and just got some extra
serial cables so maybe I can hook up a few more serial consoles and do
some additional testing.

Vince


\
 
 \ /
  Last update: 2014-04-17 17:01    [W:0.123 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site