From: Frederic Weisbecker <fweisbec@gmail.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: Sun, 17 May 2009 15:06:03 +0200 [thread overview]
Message-ID: <20090517130601.GA4640@nowhere> (raw)
In-Reply-To: <1242545498-7285-1-git-send-email-tom.leiming@gmail.com>
On Sun, May 17, 2009 at 03:31:38PM +0800, tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>
>
> return zero should be correct, so fix it.
>
> 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;
Indeed!
register_module_notifier returns blocking_notifier_chain_register():
*
* Currently always returns zero.
*/
int blocking_notifier_chain_register(struct blocking_notifier_head *nh,
struct notifier_block *n)
For now it will never return anything else than 0 but we can keep
the warning in case it changes one day, as you did.
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
next prev parent reply other threads:[~2009-05-17 13:06 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 [this message]
2009-05-18 0:54 ` Li Zefan
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=20090517130601.GA4640@nowhere \
--to=fweisbec@gmail.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