From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: fix incorrect enabling of trace events by boot cmdline
Date: Fri, 17 Apr 2015 14:10:53 +0900 [thread overview]
Message-ID: <20150417051053.GC25530@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20150416093952.1dba3052@gandalf.local.home>
On Thu, Apr 16, 2015 at 09:39:52AM -0400, Steven Rostedt wrote:
> On Thu, 16 Apr 2015 13:44:44 +0900
> Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
>
> > There is a problem that trace events are not properly enabled with
> > boot cmdline. Problem is that if we pass "trace_event=kmem:mm_page_alloc"
> > to boot cmdline, it enables all kmem trace events.
> >
> > It is caused by parsing mechanism. When we parse cmdline, buffer
> > contents is modified due to tokenization. And, if we use this buffer
> > again, we will get wrong result.
> >
> > Unfortunately, this buffer should be accessed three times
> > to set trace events properly in boot time. So, we need to handle
> > this situation.
> >
> > There is already handling code for ",", but, we need another for
> > ":". This patch add it.
>
> Thanks, but your patch has a bug in it. I'll fix it up.
>
> >
> > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> > ---
> > kernel/trace/trace_events.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> > index db54dda..ce5b194 100644
> > --- a/kernel/trace/trace_events.c
> > +++ b/kernel/trace/trace_events.c
> > @@ -565,6 +565,7 @@ static int __ftrace_set_clr_event(struct trace_array *tr, const char *match,
> > static int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
> > {
> > char *event = NULL, *sub = NULL, *match;
> > + int ret;
> >
> > /*
> > * The buf format can be <subsystem>:<event-name>
> > @@ -590,7 +591,11 @@ static int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
> > event = NULL;
> > }
> >
> > - return __ftrace_set_clr_event(tr, match, sub, event, set);
> > + ret = __ftrace_set_clr_event(tr, match, sub, event, set);
> > +
> > + /* Put back the colon to allow this to be called again */
> > + if (buf)
> > + *(buf - 1) = ':';
>
> You forgot to add:
>
> return ret;
>
Ah... my bad... :)
thanks for fixing it.
Thanks.
prev parent reply other threads:[~2015-04-17 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 4:44 Joonsoo Kim
2015-04-16 13:39 ` Steven Rostedt
2015-04-17 5:10 ` Joonsoo Kim [this message]
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=20150417051053.GC25530@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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®