From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [GIT PULL] tracing/kprobes: Fix field creation's bad error handling
Date: Wed, 9 Dec 2009 10:33:03 +0100 [thread overview]
Message-ID: <20091209093303.GD28428@elte.hu> (raw)
In-Reply-To: <4B1E3F33.2090004@redhat.com>
* Masami Hiramatsu <mhiramat@redhat.com> wrote:
> Frederic Weisbecker wrote:
> > Ingo,
> >
> > Please pull the tracing/fixes branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > tracing/fixes
> >
> > Thanks,
> > Frederic
> > ---
> >
> > Frederic Weisbecker (1):
> > tracing/kprobes: Fix field creation's bad error handling
> >
> >
> > kernel/trace/trace_kprobe.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > ---
> > From 12e22dfaaee46f70762beb1982a7b86a68317b11 Mon Sep 17 00:00:00 2001
> > From: Frederic Weisbecker <fweisbec@gmail.com>
> > Date: Tue, 8 Dec 2009 10:00:04 +0100
> > Subject: [PATCH] tracing/kprobes: Fix field creation's bad error handling
> > Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Steven Rostedt <rostedt@goodmis.org>, Masami Hiramatsu <mhiramat@redhat.com>, Li Zefan <lizf@cn.fujitsu.com>
> >
> > When we define the common event fields in kprobe, we invert the error
> > handling and return immediately in case of success. Then we omit
> > to define specific kprobes fields (ip and nargs), and specific
> > kretprobes fields (func, ret_ip, nargs). And we only define them
> > when we fail to create common fields.
> >
> > The most visible consequence is that we can't create filter for
> > k(ret)probes specific fields.
> >
> > This patch re-invert the success/error handling to fix it.
> >
> > Reported-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Steven Rostedt <rostedt@goodmis.org>
> > Cc: Masami Hiramatsu <mhiramat@redhat.com>
> > Cc: Li Zefan <lizf@cn.fujitsu.com>
>
> Thanks for fix that.
>
> Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
>
>
> Ingo, I think this should go to tip:urgent.
Will apply, thanks guys!
Ingo
next prev parent reply other threads:[~2009-12-09 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 9:16 [GIT PULL] tracing/kprobes: Fix field creation's bad error handling Frederic Weisbecker
2009-12-08 11:57 ` Masami Hiramatsu
2009-12-09 9:33 ` Ingo Molnar [this message]
2009-12-09 9:57 ` [tip:perf/urgent] " tip-bot for Frederic Weisbecker
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=20091209093303.GD28428@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mhiramat@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