From: Dmitri Vorobiev <dmitri.vorobiev@movial.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Dmitri Vorobiev <dmitri.vorobiev@movial.com>
Subject: [PATCH 2/3] Restrict definition of a label in kernel/module.c
Date: Wed, 18 Mar 2009 23:49:26 +0200 [thread overview]
Message-ID: <1237412967-20754-2-git-send-email-dmitri.vorobiev@movial.com> (raw)
In-Reply-To: <1237412967-20754-1-git-send-email-dmitri.vorobiev@movial.com>
In function 'load_module' in kernel/module.c, the label 'free_init'
is used if and only if both CONFIG_MODULE_UNLOAD and CONFIG_SMP are
defined. However, the label itself is defined unconditionally,
which may produce the following warning:
kernel/module.c:2291: warning: label 'free_init' defined but not used
This patch fixes the warning by moving the label definition under an
appropriate preprocessor construct.
Signed-off-by: Dmitri Vorobiev <dmitri.vorobiev@movial.com>
---
kernel/module.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 1196f5d..df00a1b 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -2288,8 +2288,8 @@ static noinline struct module *load_module(void __user *umod,
ftrace_release(mod->module_core, mod->core_size);
free_unload:
module_unload_free(mod);
- free_init:
#if defined(CONFIG_MODULE_UNLOAD) && defined(CONFIG_SMP)
+ free_init:
percpu_modfree(mod->refptr);
#endif
module_free(mod, mod->module_init);
--
1.5.6.3
next prev parent reply other threads:[~2009-03-18 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 21:49 [PATCH 1/3] Restrict definition of a variable in kernel/sysctl.c Dmitri Vorobiev
2009-03-18 21:49 ` Dmitri Vorobiev [this message]
2009-03-18 21:49 ` [PATCH 3/3] Restrict definition of a static function in kernel/auditsc.c Dmitri Vorobiev
2009-03-30 21:32 ` Andrew Morton
2009-03-19 7:25 ` [PATCH 1/3] Restrict definition of a variable in kernel/sysctl.c Ingo Molnar
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=1237412967-20754-2-git-send-email-dmitri.vorobiev@movial.com \
--to=dmitri.vorobiev@movial.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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®