From: Ingo Molnar <mingo@elte.hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: "Nikanth Karthikesan" <knikanth@suse.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Steven Rostedt" <srostedt@redhat.com>,
rusty@rustcorp.com.au, "Fr馘駻ic Weisbecker" <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: ftrace not working?
Date: Wed, 25 Mar 2009 08:27:29 +0100 [thread overview]
Message-ID: <20090325072729.GE25833@elte.hu> (raw)
In-Reply-To: <20090325121906.D2D6.A69D9226@jp.fujitsu.com>
* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
> >
> > ---
> >
> > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> > index 17bb88d..98f609d 100644
> > --- a/kernel/trace/trace.c
> > +++ b/kernel/trace/trace.c
> > @@ -3887,6 +3887,7 @@ __init static int tracer_alloc_buffers(void)
> >
> > register_die_notifier(&trace_die_notifier);
> > ret = 0;
> > + goto out;
> >
> > out_free_cpumask:
> > free_cpumask_var(tracing_cpumask);
>
> Good catch!
>
> I think this patch should send to 2.6.29.1 :)
a fix for that was in the tracing tree already - and will be
forwarded to .29.1 or .29.2.
Ingo
prev parent reply other threads:[~2009-03-25 7:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 6:38 ftrace not working? Nikanth Karthikesan
2009-03-23 7:15 ` Frederic Weisbecker
2009-03-23 8:41 ` Frederic Weisbecker
2009-03-23 8:44 ` Nikanth Karthikesan
2009-03-23 11:25 ` Frederic Weisbecker
2009-03-23 11:33 ` Nikanth Karthikesan
2009-03-23 8:08 ` KOSAKI Motohiro
2009-03-23 8:27 ` Nikanth Karthikesan
2009-03-23 8:35 ` Ingo Molnar
2009-03-23 8:38 ` Nikanth Karthikesan
2009-03-23 11:01 ` KOSAKI Motohiro
2009-03-23 14:32 ` Ingo Molnar
2009-03-24 17:23 ` Nikanth Karthikesan
2009-03-24 20:13 ` Frederic Weisbecker
2009-03-25 2:21 ` Steven Rostedt
2009-03-25 4:06 ` Nikanth Karthikesan
2009-03-25 4:19 ` Steven Rostedt
2009-03-25 1:08 ` Rusty Russell
2009-03-25 3:21 ` KOSAKI Motohiro
2009-03-25 7:27 ` Ingo Molnar [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=20090325072729.GE25833@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=knikanth@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=srostedt@redhat.com \
/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