From: "Jan Beulich" <jbeulich@novell.com>
To: <sam@ravnborg.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: kbuild: fix section mismatch check for vmlinux
Date: Mon, 11 Jun 2007 10:25:59 +0200 [thread overview]
Message-ID: <466D2337.76E4.0078.0@novell.com> (raw)
>vmlinux does not contain relocation entries which is
>used by the section mismatch checks.
>Reported by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
>
>Use the individual objects as inputs to overcome
>this limitation.
>In modpost check the .o files and skip non-ELF files.
>
>Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
This still doesn't appear to catch all cases - since the checking logic works
on a per-module basis, references between the individual .o files aren't
being checked. A current instance where this is visible is x86-64's recently
added alloc_bootmem_high_node (non-__init, in arch/x86_64/mm/built-in.o)
calling __alloc_bootmem_core (__init, in mm/built-in.o). I suppose there's
no way around linking $(KBUILD_VMLINUX_OBJS) into vmlinux.o, and
checking that file instead.
Jan
next reply other threads:[~2007-06-11 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 8:25 Jan Beulich [this message]
2007-06-11 21:50 ` 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=466D2337.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--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
all inboxes | Powered by JetHome®