Messages in this thread | | | Date | Wed, 7 May 2014 21:11:42 +0200 | From | Ingo Molnar <> | Subject | Re: [perf] more perf_fuzzer memory corruption |
| |
* Vince Weaver <vincent.weaver@maine.edu> wrote:
> On Mon, 5 May 2014, Ingo Molnar wrote: > > > > I'm also thinking about waiting a bit before applying anything even > > borderline intrusive to the perf core, to make sure there's enough > > fuzz time to declare stable state (at least as far into the ABI as the > > fuzzing is able to reach). Future bisection efforts could use that > > kind of known-stable release. > > That does sound like a good idea. It is nice finally getting to the > state where you can fuzz for hours (rather than minutes) without > hitting a bug. > > Of course that might change. Development of the fuzzer has more or > less stalled for the past 6 months as I was spending all of my time > reporting/chasing bugs rather than enhancing the fuzzer. > > In any case if we can get the recent patches applied in time for > 3.15 I think it will turn out to be a nice release > perf-event-stability wise.
Yeah, I'm trying to get them all into v3.15 - and if they prove out fine they might be backportable further as well.
Thanks,
Ingo
| |