From: Li Zefan <lizf@cn.fujitsu.com>
To: tom.leiming@gmail.com
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, mingo@elte.hu
Subject: Re: [PATCH] ftrace:fix check for return value of register_module_notifier
Date: Mon, 18 May 2009 08:54:12 +0800 [thread overview]
Message-ID: <4A10B1B4.5080309@cn.fujitsu.com> (raw)
In-Reply-To: <1242545498-7285-1-git-send-email-tom.leiming@gmail.com>
tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>
>
> return zero should be correct, so fix it.
>
Nice catch.
We have those bogus warnings:
$ dmesg | grep Failed
Failed to register trace ftrace module notifier
Failed to register trace events module notifier
Could you fix the same bug in event_trace_init()?
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> ---
> kernel/trace/ftrace.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 5b606f4..140699a 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -2826,7 +2826,7 @@ void __init ftrace_init(void)
> __stop_mcount_loc);
>
> ret = register_module_notifier(&ftrace_module_nb);
> - if (!ret)
> + if (ret)
> pr_warning("Failed to register trace ftrace module notifier\n");
>
> return;
next prev parent reply other threads:[~2009-05-18 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 7:31 [PATCH] ftrace:fix check for return value of register_module_notifier tom.leiming
2009-05-17 13:06 ` Frederic Weisbecker
2009-05-18 0:54 ` Li Zefan [this message]
2009-05-18 1:40 ` Ming Lei
2009-05-18 12:39 ` Ming Lei
2009-05-18 14:25 ` Frederic Weisbecker
2009-05-18 15:11 ` Ming Lei
2009-05-18 9:06 ` [tip:tracing/core] tracing: fix " tip-bot for Ming Lei
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=4A10B1B4.5080309@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tom.leiming@gmail.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