From: Randy Dunlap <randy.dunlap@oracle.com>
To: virtualization@lists.osdl.org
Cc: akpm <akpm@osdl.org>, sam@ravnborg.org
Subject: Section mismatch in parainstructions
Date: Sun, 10 Dec 2006 15:58:21 -0800 [thread overview]
Message-ID: <20061210155821.d2c5dfa5.randy.dunlap@oracle.com> (raw)
Is it OK for section .parainstructions to reference
exit.text?
I'm seeing:
WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x0)
WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x8)
If that's OK, we need a small patch to modpost, as below.
---
~Randy
From: Randy Dunlap <randy.dunlap@oracle.com>
Section .parainstructions should not warn about section mismatches.
WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x0)
WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x8)
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
scripts/mod/modpost.c | 1 +
1 file changed, 1 insertion(+)
--- linux-2.6.19-git17.orig/scripts/mod/modpost.c
+++ linux-2.6.19-git17/scripts/mod/modpost.c
@@ -997,6 +997,7 @@ static int exit_section_ref_ok(const cha
"__bug_table", /* used by powerpc for BUG() */
".exitcall.exit",
".eh_frame",
+ ".parainstructions",
".stab",
"__ex_table",
".fixup",
next reply other threads:[~2006-12-10 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 23:58 Randy Dunlap [this message]
2006-12-11 0:40 ` Section mismatch in parainstructions Jeremy Fitzhardinge
2006-12-11 2:34 ` Randy Dunlap
2006-12-11 9:34 ` Jeremy Fitzhardinge
2006-12-12 0:14 ` Rusty Russell
2006-12-12 3:21 ` Andi Kleen
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=20061210155821.d2c5dfa5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=sam@ravnborg.org \
--cc=virtualization@lists.osdl.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