Re: task_ctx_sched_out WARN_ON triggered.

2014-02-14 Thread Dave Jones
On Wed, Jan 29, 2014 at 04:32:04PM +0100, Peter Zijlstra wrote: > On Wed, Jan 29, 2014 at 03:07:44PM +0100, Peter Zijlstra wrote: > > Let me see if I can make a 'nice' function to dump state though, it > > might come in handy more often. > > Compile tested only... This took a while, but I fi

Re: task_ctx_sched_out WARN_ON triggered.

2014-01-29 Thread Peter Zijlstra
On Wed, Jan 29, 2014 at 03:07:44PM +0100, Peter Zijlstra wrote: > Let me see if I can make a 'nice' function to dump state though, it > might come in handy more often. Compile tested only... --- include/linux/perf_event.h | 4 ++ init/Kconfig | 7 ++ kernel/events/core.c

Re: task_ctx_sched_out WARN_ON triggered.

2014-01-29 Thread Peter Zijlstra
On Tue, Jan 21, 2014 at 10:09:53AM -0500, Dave Jones wrote: > On Fri, Jan 10, 2014 at 11:48:37AM +0100, Peter Zijlstra wrote: > > On Thu, Jan 09, 2014 at 10:47:07AM -0500, Dave Jones wrote: > > > This is my fuzz tester, but this looks to be part of normal operation, > > > not actually fuzzing a

Re: task_ctx_sched_out WARN_ON triggered.

2014-01-21 Thread Dave Jones
On Fri, Jan 10, 2014 at 11:48:37AM +0100, Peter Zijlstra wrote: > On Thu, Jan 09, 2014 at 10:47:07AM -0500, Dave Jones wrote: > > This is my fuzz tester, but this looks to be part of normal operation, > > not actually fuzzing a syscall. This looks to be the bit that > > sets the task_comm name

Re: task_ctx_sched_out WARN_ON triggered.

2014-01-10 Thread Dave Jones
On Fri, Jan 10, 2014 at 11:48:37AM +0100, Peter Zijlstra wrote: > On Thu, Jan 09, 2014 at 10:47:07AM -0500, Dave Jones wrote: > > This is my fuzz tester, but this looks to be part of normal operation, > > not actually fuzzing a syscall. This looks to be the bit that > > sets the task_comm name

Re: task_ctx_sched_out WARN_ON triggered.

2014-01-10 Thread Peter Zijlstra
On Thu, Jan 09, 2014 at 10:47:07AM -0500, Dave Jones wrote: > This is my fuzz tester, but this looks to be part of normal operation, > not actually fuzzing a syscall. This looks to be the bit that > sets the task_comm name in the child process to 'trinity-cN'. Which appears > to have > succeeded

task_ctx_sched_out WARN_ON triggered.

2014-01-09 Thread Dave Jones
This is my fuzz tester, but this looks to be part of normal operation, not actually fuzzing a syscall. This looks to be the bit that sets the task_comm name in the child process to 'trinity-cN'. Which appears to have succeeded judging by the Comm:, but the follow-on perf stuff seems to be screwed