From: Don Zickus <dzickus@redhat.com>
To: <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Don Zickus <dzickus@redhat.com>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH] x86,nmi: Fix section mismatch warnings on 32-bit
Date: Mon, 4 Jun 2012 15:56:03 -0400 [thread overview]
Message-ID: <1338839763-11140-1-git-send-email-dzickus@redhat.com> (raw)
It was reported that compiling for 32-bit caused a bunch of section
mismatch warnings:
VDSOSYM arch/x86/vdso/vdso32-syms.lds
LD arch/x86/vdso/built-in.o
LD arch/x86/built-in.o
WARNING: arch/x86/built-in.o(.data+0x5af0): Section mismatch in reference from the variable
test_nmi_ipi_callback_na.10451 to the function .init.text:test_nmi_ipi_callback()
The variable test_nmi_ipi_callback_na.10451 references
the function __init test_nmi_ipi_callback()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
WARNING: arch/x86/built-in.o(.data+0x5b04): Section mismatch in reference from the variable
nmi_unk_cb_na.10399 to the function .init.text:nmi_unk_cb()
The variable nmi_unk_cb_na.10399 references
the function __init nmi_unk_cb()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
Both of these are attributed to the callback functions of this self contained
test. It seems this happened when the function added new __init sections in
commit f0ba662.
I fixed this by converting the callback functions from __init to __ref. The file
compiles and boots on my machine for 32-bit and 64-bit.
Not sure why 64-bit never showed this warning. Nor am I entirely sure why this
warning popped up to begin with.
Let me know if there is a better way to fix this.
Reported-by: Witold Baryluk <baryluk@smp.if.uj.edu.pl>
Cc: Jan Beulich <JBeulich@suse.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
---
arch/x86/kernel/nmi_selftest.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/nmi_selftest.c b/arch/x86/kernel/nmi_selftest.c
index e31bf8d..692e453 100644
--- a/arch/x86/kernel/nmi_selftest.c
+++ b/arch/x86/kernel/nmi_selftest.c
@@ -33,7 +33,7 @@ static int __initdata expected_testcase_failures;
static int __initdata unexpected_testcase_failures;
static int __initdata unexpected_testcase_unknowns;
-static int __init nmi_unk_cb(unsigned int val, struct pt_regs *regs)
+static int __ref nmi_unk_cb(unsigned int val, struct pt_regs *regs)
{
unexpected_testcase_unknowns++;
return NMI_HANDLED;
@@ -50,7 +50,7 @@ static void __init cleanup_nmi_testsuite(void)
unregister_nmi_handler(NMI_UNKNOWN, "nmi_selftest_unk");
}
-static int __init test_nmi_ipi_callback(unsigned int val, struct pt_regs *regs)
+static int __ref test_nmi_ipi_callback(unsigned int val, struct pt_regs *regs)
{
int cpu = raw_smp_processor_id();
--
1.7.7.6
next reply other threads:[~2012-06-04 19:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:56 Don Zickus [this message]
2012-06-05 8:12 ` Jan Beulich
2012-06-05 14:47 ` Don Zickus
2012-06-05 15:42 ` Jan Beulich
2012-06-05 18:35 ` Don Zickus
2012-06-06 11:14 ` Jan Beulich
2012-06-06 14:03 ` Don Zickus
2012-06-06 15:45 ` Ingo Molnar
2012-06-06 18:28 ` Don Zickus
2012-06-07 7:43 ` Li Zhong
2012-06-07 12:48 ` Don Zickus
2012-06-08 20:51 ` Don Zickus
2012-06-11 1:36 ` Zhong Li
2012-06-11 8:19 ` Ingo Molnar
2012-06-05 16:13 ` Sam Ravnborg
2012-06-05 16:18 ` Jan Beulich
2012-06-05 17:22 ` Sam Ravnborg
2012-06-08 2:06 ` Don Zickus
2012-06-08 5:40 ` Sam Ravnborg
2012-06-06 14:05 Don Zickus
2012-06-06 21:22 ` Witold Baryluk
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=1338839763-11140-1-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=JBeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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®