From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Chris Wedgwood <cw@f00f.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: (hacky) [PATCH] silence MODPOST section mismatch warnings
Date: Thu, 10 May 2007 21:40:38 +0100 [thread overview]
Message-ID: <20070510204037.GE29713@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070510203417.GA23019@tuatara.stupidest.org>
On Thu, May 10, 2007 at 01:34:18PM -0700, Chris Wedgwood wrote:
> MODPOST seems to be spewing bogus warnings. It's not clear how best
> to fix it so perhaps we should silence it for now?
I agree. Example bogus warning:
WARNING: arch/arm/mach-iop32x/built-in.o - Section mismatch:
reference to .init.text: from .data between 'iq80321_timer'
(at offset 0x428) and 'iq80321_serial_device'
c04088fc d iq80321_timer
c0408950 d iq80321_serial_device
It's completely unclear what is referencing what, what the two named
symbols mean, and even what "at offset" relates to.
What I can say is that iq80321_timer doesn't reference iq80321_serial_device
nor vice versa, and iq80321_timer is far smaller than 0x428 bytes.
>
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 113dc77..bd6fe7b 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -872,6 +872,10 @@ static void warn_sec_mismatch(const char *modname, const char *fromsec,
> sechdrs[hdr->e_shstrndx].sh_offset;
> const char *secname = secstrings + sechdrs[sym->st_shndx].sh_name;
>
> + /* FIXME: this function doesn't work correctly anymore, it's
> + * not clear if it should be fixed or removed. */
> + return;
> +
> find_symbols_between(elf, r.r_offset, fromsec, &before, &after);
>
> refsym = find_elf_symbol(elf, r.r_addend, sym);
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-05-10 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:34 (hacky) [PATCH] silence MODPOST section mismatch warnings Chris Wedgwood
2007-05-10 20:40 ` Russell King [this message]
2007-05-10 21:01 ` David Miller
2007-05-10 21:14 ` Sam Ravnborg
2007-05-10 20:51 ` David Miller
2007-05-10 20:54 ` Russell King
2007-05-10 21:01 ` Sam Ravnborg
2007-05-11 6:28 ` Satyam Sharma
2007-05-10 21:07 ` David Miller
2007-05-10 21:23 ` Russell King
2007-05-10 21:59 ` Russell King
2007-05-10 22:03 ` [PATCH] Make modpost section warnings clearer Russell King
2007-05-10 22:08 ` David Miller
2007-05-10 22:16 ` (hacky) [PATCH] silence MODPOST section mismatch warnings Sam Ravnborg
2007-05-10 22:18 ` Russell King
2007-05-11 4:12 ` Sam Ravnborg
2007-05-11 18:54 ` Sam Ravnborg
2007-05-11 18:57 ` Russell King
2007-05-10 21:19 ` Sam Ravnborg
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=20070510204037.GE29713@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=cw@f00f.org \
--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