From: Sam Ravnborg <sam@ravnborg.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [PATCH] kbuild: make better section mismatch reports on i386 and mips
Date: Tue, 15 May 2007 22:47:54 +0200 [thread overview]
Message-ID: <20070515204754.GD22966@uranus.ravnborg.org> (raw)
In-Reply-To: <20070515.004035.21363504.anemo@mba.ocn.ne.jp>
On Tue, May 15, 2007 at 12:40:35AM +0900, Atsushi Nemoto wrote:
> On i386 and MIPS, warn_sec_mismatch() sometimes fails to show usefull
> symbol name. This is because empty 'refsym' due to 0 r_addend value.
> This patch is to adjust r_addend value, consulting with
> apply_relocate() routine in kernel code.
>
> Without this patch:
> MODPOST vmlinux
> WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xf4) and 'try_name'
> WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
> WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'
>
> With this patch:
> MODPOST vmlinux
> WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
> WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'
>
> Now modpost can detect "kernel_init" name (and whitelist it) and show
> "set_up_list3s" name.
Applied.
It seems arm is impacted by the same.
Can you add arm support for the same?
Sam
next prev parent reply other threads:[~2007-05-15 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:40 Atsushi Nemoto
2007-05-15 20:47 ` Sam Ravnborg [this message]
2007-05-16 16:14 ` Atsushi Nemoto
2007-05-17 7:07 ` 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=20070515204754.GD22966@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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
Powered by JetHome