linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatch warnings
Date: Fri, 23 Jun 2006 23:22:43 +0100	[thread overview]
Message-ID: <20060623222243.GB27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20060623221217.GA372@mars.ravnborg.org>

On Sat, Jun 24, 2006 at 12:12:18AM +0200, Sam Ravnborg wrote:
> On Fri, Jun 23, 2006 at 07:40:12PM +0200, Jan Engelhardt wrote:
> > Hello,
> > 
> > 
> > as others have already seen to, 2.6.17 spits out a lot of section mismatch 
> > warnings on modpost. Some of them have may already been addressed; here is 
> > the output I get when MODPOST starts to run during the compile process of 
> > an almost-completely-compiled kernel. Need .config?
> 
> All the .smp_locks related warnings are gone when I get the kbuild.git
> tree pushed linus wise. Needs to spend only an hour or so before it is
> ready and will do so during the weekend.

BTW, I've also got some modpost.c patches dealing with false positives
(as well as fixes for real crap).  modpost.c delta follows, just in case
if some of that might be missing from your tree

>From nobody Mon Sep 17 00:00:00 2001
From: Al Viro <viro@zeniv.linux.org.uk>
Date: Wed, 14 Jun 2006 13:05:12 -0400
Subject: [PATCH] kill some false positives from modpost

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

---

 scripts/mod/modpost.c |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

919db28eefd21a9c9f7d790c9f37694bad3a0b9a
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 0b92ddf..cd94d6a 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -768,6 +768,8 @@ static int init_section_ref_ok(const cha
 		".pci_fixup_final",
 		".pdr",
 		"__param",
+		"__ex_table",
+		".fixup",
 		NULL
 	};
 	/* Start of section names */
@@ -793,6 +795,8 @@ static int init_section_ref_ok(const cha
 	for (s = namelist3; *s; s++)
 		if (strstr(name, *s) != NULL)
 			return 1;
+	if (strrcmp(name, ".init") == 0)
+		return 1;
 	return 0;
 }
 
@@ -837,6 +841,8 @@ static int exit_section_ref_ok(const cha
 		".exitcall.exit",
 		".eh_frame",
 		".stab",
+		"__ex_table",
+		".fixup",
 		NULL
 	};
 	/* Start of section names */
-- 
1.3.GIT


  reply	other threads:[~2006-06-23 22:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 17:40 Section mismatch warnings Jan Engelhardt
2006-06-23 22:12 ` Sam Ravnborg
2006-06-23 22:22   ` Al Viro [this message]
2006-06-24 21:02     ` Sam Ravnborg
2006-06-23 22:23   ` Al Viro
2006-06-26 12:37     ` Roman Zippel
2007-07-30 17:48 Gabriel C
2007-07-30 18:51 ` Sam Ravnborg
2007-07-30 19:31   ` Gabriel C
2007-07-31 19:45     ` Gabriel C
2007-07-31 20:48       ` Sam Ravnborg
2007-07-31 21:58         ` Gabriel C
2007-08-02 14:27           ` Gabriel C
2007-08-02 16:31             ` Sam Ravnborg
2007-08-02 17:12               ` Gabriel C
2007-08-02 17:59                 ` Sam Ravnborg
2007-08-02 18:24                   ` Gabriel C

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=20060623222243.GB27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).