public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Magnus Damm <magnus@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org, fastboot@lists.osdl.org,
	ebiederm@xmission.com
Subject: Re: [PATCH] CONFIG_RELOCATABLE modpost fix
Date: Wed, 9 Aug 2006 08:29:18 +0200	[thread overview]
Message-ID: <20060809062918.GA10903@mars.ravnborg.org> (raw)
In-Reply-To: <1155087156.4341.66.camel@localhost>

On Wed, Aug 09, 2006 at 10:32:36AM +0900, Magnus Damm wrote:
 
> Your patch seems to work as expected if I add a return 0 at the end of
> modpost.c:secref_whitelist(). I like how you printed out the number of
> modules being processed.
Thanks - fixed now. My gcc (3.4.6-r1 from Gentoo did not warn)

>I have one minor comment about your patch:
> 
> Modpost seems to get run twice on vmlinux if the kernel is built with
> "make all". I think it would be best to run modpost on vmlinux only when
> vmlinux is built - never when modules are processed.

Thesecond time modpost runs vmlinux is used to pick up symbol
information to check that all symbols are valid etc.
The alternative was to trust the symbols being read from Module.symvers
and that would be OK in most cases but I could imagine situations where
Module.symvers was deleted but vmlinux kept.

So therefore the more expensive solution to run modpost twice on vmlinux
was chosen.

	Sam

  reply	other threads:[~2006-08-09  6:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  8:32 [PATCH] CONFIG_RELOCATABLE modpost fix Magnus Damm
2006-08-08 15:16 ` Sam Ravnborg
2006-08-09  1:12   ` Magnus Damm
2006-08-08 18:39 ` Sam Ravnborg
2006-08-08 19:59   ` Eric W. Biederman
2006-08-08 22:05     ` Sam Ravnborg
2006-08-09  1:32   ` Magnus Damm
2006-08-09  6:29     ` Sam Ravnborg [this message]
2006-08-09  7:06       ` Magnus Damm

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=20060809062918.GA10903@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    /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