Re: [perf] more perf_fuzzer memory corruption

[Peter Zijlstra]

On Thu, May 01, 2014 at 12:51:33AM +0200, Thomas Gleixner wrote:
> And that's the issue which puzzles us. Let's look at what we expect:
> 
> Now the trace shows a different story:
> 
>      perf_fuzzer-4387  [001]  1802.628659: sys_enter:            NR 298 (69bb58, 0, ffffffff, 12, 0, 0)

That's a per-cpu event (.pid = -1, .cpu = 12), they don't get inherited,
so the only thing keeping it alive is the fd the child got. So
exit_files() killing this thing makes perfect sense.

Onwards to find another funny.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/