Date: Wed, 28 Aug 2013 12:50:36 -0400 (EDT)
From: Vince Weaver <vince@deater.net>
To: Dave Jones <davej@redhat.com>
cc: Steven Rostedt <rostedt@goodmis.org>,
        Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
In-Reply-To: <20130828162321.GA14689@redhat.com>
Message-ID: <alpine.DEB.2.02.1308281245370.6937@pianoman.cluster.toy>
References: <20130828034627.GA30596@redhat.com> <20130828103101.3f5679bc@gandalf.local.home> <20130828162321.GA14689@redhat.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1196
Lines: 26

On Wed, 28 Aug 2013, Dave Jones wrote:
> Quite often just rerunning that last syscall that caused the oops/warn
> isn't sufficient to trigger an issue. (Though it may be for this specific
> bug that may not be the case..)
> 
> Vince has a variant of trinity focussed just on perf which also has some
> neat replay/bisecting capabilities to narrow down test cases.
> I think I might need to add something like that at some point.

Yes, you can get the perf_fuzzer code here:
   git clone https://github.com/deater/perf_event_tests.git
in the fuzzer directory

Bisecting down which perf_event_open() call causes problems is still very 
labor intensive even with the other tools I've added to help.  Even if the 
bug is triggered right away (within the first 100,000 calls or so) it can 
take hours to narrow things down to the two or three syscalls needed to 
reproduce the problem.  Especially if you need to reboot after triggering 
the issue.

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