From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Subject: Re: linux-next: rr tree build warning
Date: Thu, 12 Nov 2009 23:45:48 +1030 [thread overview]
Message-ID: <200911122345.49100.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20091112192114.dcf32d16.sfr@canb.auug.org.au>
On Thu, 12 Nov 2009 06:51:14 pm Stephen Rothwell wrote:
> Hi Rusty,
>
> Today's linux-next build (i386 defconfig) produced this warning:
>
> kernel/module.c:1953: warning: 'crc_section_names' defined but not used
>
> Introduced by commit 67260d90118a2394df528fe4e37e814d950ca5b5 ("module:
> refactor symbol tables and try to reduce code size of each_symbol()").
> This build has CONFIG_MODVERSIONS disabled.
Thanks. I hit that warning in my config too, but didn't notice :(
Subject: Fix warning for CONFIG_MODVERSIONS=n:
linux-next Maestro Stephen Rothwell reports:
Today's linux-next build (i386 defconfig) produced this warning:
kernel/module.c:1953: warning: 'crc_section_names' defined but not used
Introduced by commit 67260d90118a2394df528fe4e37e814d950ca5b5 ("module:
refactor symbol tables and try to reduce code size of each_symbol()").
This build has CONFIG_MODVERSIONS disabled.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff --git a/kernel/module.c b/kernel/module.c
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -1075,6 +1075,16 @@ static int try_to_force_load(struct modu
}
#ifdef CONFIG_MODVERSIONS
+static const char *crc_section_names[] = {
+ [EXPORT_TYPE_PLAIN] = "__kcrctab",
+ [EXPORT_TYPE_GPL] = "__kcrctab_gpl",
+#ifdef CONFIG_UNUSED_SYMBOLS
+ [EXPORT_TYPE_UNUSED] = "__kcrctab_unused",
+ [EXPORT_TYPE_UNUSED_GPL] = "__kcrctab_unused_gpl",
+#endif
+ [EXPORT_TYPE_GPL_FUTURE] = "__kcrctab_gpl_future",
+};
+
static int check_version(Elf_Shdr *sechdrs,
unsigned int versindex,
const char *symname,
@@ -2103,16 +2113,6 @@ static const char *export_section_names[
[EXPORT_TYPE_GPL_FUTURE] = "__ksymtab_gpl_future",
};
-static const char *crc_section_names[] = {
- [EXPORT_TYPE_PLAIN] = "__kcrctab",
- [EXPORT_TYPE_GPL] = "__kcrctab_gpl",
-#ifdef CONFIG_UNUSED_SYMBOLS
- [EXPORT_TYPE_UNUSED] = "__kcrctab_unused",
- [EXPORT_TYPE_UNUSED_GPL] = "__kcrctab_unused_gpl",
-#endif
- [EXPORT_TYPE_GPL_FUTURE] = "__kcrctab_gpl_future",
-};
-
/* Allocate and load the module: note that size of section 0 is always
zero, and we rely on this for optional sections. */
static noinline struct module *load_module(void __user *umod,
next prev parent reply other threads:[~2009-11-12 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 8:21 linux-next: rr tree build warning Stephen Rothwell
2009-11-12 13:15 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 3:58 Stephen Rothwell
2009-06-09 6:26 Stephen Rothwell
2009-06-10 6:40 ` Rusty Russell
2009-06-10 6:46 ` Stephen Rothwell
2009-01-08 4:54 Stephen Rothwell
2008-12-04 23:42 Stephen Rothwell
2008-10-24 2:34 Stephen Rothwell
2008-10-24 3:44 ` Rusty Russell
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=200911122345.49100.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).