lkml.org 
[lkml]   [2014]   [May]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [perf] more perf_fuzzer memory corruption
On Mon, 5 May 2014, Peter Zijlstra wrote:

> Cute.. does the below cure?
>
>
> ---
> Subject: perf: Fix perf_event_init_context()
> From: Peter Zijlstra <peterz@infradead.org>
> Date: Mon May 5 19:12:20 CEST 2014
>
> perf_pin_task_context() can return NULL but perf_event_init_context()
> assumes it will not, correct this.

It makes the oops go away, but it does make the fuzzer become unkillable
while using 100% CPU.

It looks like it is stuck repeating this forever:
perf_fuzzer-5256 [000] 275.943049: kmalloc: (T.1262+0xe) call_site=ffffffff810d022f ptr=0xffff8800cb028400 bytes_req=216 bytes_alloc=256 gfp_flags=GFP_KERNEL|GFP_ZERO
perf_fuzzer-5256 [000] 275.943057: function: perf_lock_task_context
perf_fuzzer-5256 [000] 275.943057: function: alloc_perf_context
and memory is slowly leaking away.


Meanwhile the haswell and AMD machines have been fuzzing away without
issue, I don't know why the core2 machine is always the trouble maker.

Vince



\
 
 \ /
  Last update: 2014-05-05 21:21    [W:0.237 / U:0.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site