Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-08 Thread Peter Zijlstra
On Mon, Jul 08, 2013 at 06:50:23PM +0200, Peter Zijlstra wrote: > > [ 324.983534] [ cut here ] > [ 324.984420] WARNING: at /usr/src/linux-2.6/kernel/events/core.c:1953 > __perf_event_enable+0x187/0x190() > [ 324.984420] Modules linked in: > [ 324.984420] CPU: 19 PID: 2

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-08 Thread Peter Zijlstra
On Mon, Jul 08, 2013 at 03:50:48PM +0200, Jiri Olsa wrote: > need to check if that does not break anything else ;-) Vince's test-case triggered the below; so there might still be a few loose ends. [ 324.983534] [ cut here ] [ 324.984420] WARNING: at /usr/src/linux-2.6/

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-08 Thread Peter Zijlstra
On Mon, Jul 08, 2013 at 03:50:48PM +0200, Jiri Olsa wrote: > patch below gets rid of the warning, and probably the > crash as well > > the reason seems to be when HW context is cloned based > on SW event that happened to get there because of the > HW leader, which got closed just before (fd[15] ev

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-08 Thread Vince Weaver
On Mon, 8 Jul 2013, Jiri Olsa wrote: > On Wed, Jul 03, 2013 at 09:49:29AM +0200, Peter Zijlstra wrote: > > On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote: > need to check if that does not break anything else ;-) I've applied your patch to stock 3.10 and am now unable to hang my Core

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-08 Thread Jiri Olsa
On Wed, Jul 03, 2013 at 09:49:29AM +0200, Peter Zijlstra wrote: > On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote: > > > > OK, I have bisected this problem to the following change: > > > > commit 8dc85d547285668e509f86c177bcd4ea055bcaaf > > Author: Peter Zijlstra > > Date: Thu Sep

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-03 Thread Peter Zijlstra
On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote: > > OK, I have bisected this problem to the following change: > > commit 8dc85d547285668e509f86c177bcd4ea055bcaaf > Author: Peter Zijlstra > Date: Thu Sep 2 16:50:03 2010 +0200 > > perf: Multiple task contexts > > Prov

Re: [bisected] perf: yet another fuzzer triggered crash

2013-07-02 Thread Vince Weaver
OK, I have bisected this problem to the following change: commit 8dc85d547285668e509f86c177bcd4ea055bcaaf Author: Peter Zijlstra Date: Thu Sep 2 16:50:03 2010 +0200 perf: Multiple task contexts Provide the infrastructure for multiple task contexts. -- To unsubscribe from this li