From: Sasha Levin <sasha.levin@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vince Weaver <vincent.weaver@maine.edu>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [GIT PULL] tracing: Have filter check for balanced ops
Date: Thu, 25 Jun 2015 16:11:46 -0400 [thread overview]
Message-ID: <558C6082.90608@oracle.com> (raw)
In-Reply-To: <20150625003510.1ea5a750@grimm.local.home>
On 06/25/2015 12:35 AM, Steven Rostedt wrote:
> On Thu, 25 Jun 2015 00:03:02 -0400
> Sasha Levin <sasha.levin@oracle.com> wrote:
>
>> On 06/17/2015 08:36 AM, Steven Rostedt wrote:
>>> Linus,
>>>
>>> Vince Weaver reported a warning when he added perf event filters
>>> into his fuzzer tests. There's a missing check of balanced
>>> operations when parenthesis are used, and this triggers a WARN_ON()
>>> and when reading the failure, the filter reports no failure occurred.
>>
>> Hey Steven,
>>
>> My fuzzings are hitting the warning added by this patch:
>
> Yes, Vince said he was able to hit it as well. But the warning itself
> is useless if you don't supply what filter was used to trigger it.
# echo ">" > events/ext4/ext4_truncate_exit/filter
Thanks,
Sasha
next prev parent reply other threads:[~2015-06-25 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 12:36 [GIT PULL] tracing: Have filter check for balanced ops Steven Rostedt
2015-06-22 13:53 ` Luis Henriques
2015-06-22 14:03 ` Luis Henriques
2015-06-22 14:17 ` Steven Rostedt
2015-06-22 14:49 ` Luis Henriques
2015-06-24 14:54 ` Greg KH
2015-06-25 4:03 ` Sasha Levin
2015-06-25 4:35 ` Steven Rostedt
2015-06-25 20:11 ` Sasha Levin [this message]
2015-06-25 23:08 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558C6082.90608@oracle.com \
--to=sasha.levin@oracle.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox