Messages in this thread Patch in this message | | | Date | Fri, 2 May 2014 22:45:09 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: [perf] more perf_fuzzer memory corruption |
| |
On Fri, 2 May 2014, Vince Weaver wrote:
> On Fri, 2 May 2014, Thomas Gleixner wrote: > > > Hmm, and where comes the WARN_ON in _free_event() from? That's not in > > Peters last patch. > > ahh, you're right :( My fault. I gave the new patch and the previous > patch similar names and applied the wrong one. > > OK the proper patch has been running the quick reproducer for a bit > without triggering the issue, I'll let it run a bit more and then upgrade > to full fuzzing.
If you do that, please add the patch below.
Thanks,
tglx
Index: linux-2.6/kernel/events/core.c =================================================================== --- linux-2.6.orig/kernel/events/core.c +++ linux-2.6/kernel/events/core.c @@ -7378,7 +7378,7 @@ __perf_event_exit_task(struct perf_event struct perf_event_context *child_ctx, struct task_struct *child) { - perf_remove_from_context(child_event, !!child_event->parent); + perf_remove_from_context(child_event, true); /* * It can happen that the parent exits first, and has events
| |