From: Steven Rostedt <rostedt@goodmis.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] tracing/filters: Support filtering for char * strings
Date: Thu, 6 Aug 2009 23:31:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908062328140.2840@gandalf.stny.rr.com> (raw)
In-Reply-To: <4A7B9E6B.2090202@cn.fujitsu.com>
On Fri, 7 Aug 2009, Li Zefan wrote:
> Steven Rostedt wrote:
> > Ah, so the answer I'm looking for is:
> >
> > The filtering will not dereference "char *" unless the developer
> > explicitly sets FILTER_PTR_STR in __field_ext.
> >
> > Is this above statement correct?
> >
>
> Exactly. Sorry that I didn't explain it clearly in the
> first place. :)
No problem. It is quite often that things so blatantly obvious to a
developer is totally foreign for the observer, that the simple explanation
is commonly overlooked.
I'll pull in your patches, with the -1 update, as well as adding my
above statement to this patch's change log.
I'll queue it for 32.
Thanks!
-- Steve
next prev parent reply other threads:[~2009-08-07 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 6:05 [PATCH 0/3] tracing/filters: Support specifying filter hook to a TRACE_EVENT field Li Zefan
2009-08-06 6:06 ` [PATCH 1/3] tracing/filters: Add filter_type to struct ftrace_event_field Li Zefan
2009-08-06 6:06 ` [PATCH 2/3] tracing/filters: Add __field_ext() to TRACE_EVENT Li Zefan
2009-08-06 14:17 ` Steven Rostedt
2009-08-06 6:06 ` [PATCH 3/3] tracing/filters: Support filtering for char * strings Li Zefan
2009-08-06 14:21 ` Steven Rostedt
2009-08-07 1:20 ` Li Zefan
2009-08-07 2:54 ` Steven Rostedt
2009-08-07 3:12 ` Li Zefan
2009-08-07 3:22 ` Steven Rostedt
2009-08-07 3:24 ` Li Zefan
2009-08-07 3:31 ` Steven Rostedt [this message]
2009-08-06 14:23 ` [PATCH 0/3] tracing/filters: Support specifying filter hook to a TRACE_EVENT field Steven Rostedt
2009-08-07 1:08 ` Li Zefan
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=alpine.DEB.2.00.0908062328140.2840@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®