From: Vince Weaver <vincent.weaver@maine.edu>
Date: Fri, 12 Jun 2015 21:15:10 -0400 (EDT)
To: Steven Rostedt <rostedt@goodmis.org>
cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf,ftrace: fuzzer triggers warning in trace_events_filter
 code
In-Reply-To: <20150612174045.1e9b0ca0@gandalf.local.home>
Message-ID: <alpine.DEB.2.20.1506122113580.5662@vincent-weaver-1.umelst.maine.edu>
References: <alpine.DEB.2.20.1506121713340.5186@vincent-weaver-1.umelst.maine.edu> <20150612174045.1e9b0ca0@gandalf.local.home>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 737
Lines: 24

On Fri, 12 Jun 2015, Steven Rostedt wrote:

> On Fri, 12 Jun 2015 17:18:22 -0400 (EDT)
> Vince Weaver <vincent.weaver@maine.edu> wrote:
> 
> > 
> > So I've modified my fuzzer to try to exercise the 
> > PERF_EVENT_IOC_SET_FILTER ioctl() and it is starting to turn up some 
> > warnings.
> 
> Is there any way to know what the filter string you used that generated
> this?

Various seem to trigger it.  One example is

	ext4:ext4_truncate_exit
	(((dev<=913)blocks==916)common_type&756)

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/