mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Magnus Damm <magnus@valinux.co.jp>,
	linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: [PATCH] CONFIG_RELOCATABLE modpost fix
Date: Wed, 9 Aug 2006 00:05:09 +0200	[thread overview]
Message-ID: <20060808220509.GA8378@mars.ravnborg.org> (raw)
In-Reply-To: <m17j1j6ltk.fsf@ebiederm.dsl.xmission.com>

On Tue, Aug 08, 2006 at 01:59:03PM -0600, Eric W. Biederman wrote:
 
> Sam, Magnus: 
> 
> I'm dense.  Why do we want to run modpost if we are building a kernel
> that doesn't support modules?
> 
> I haven't mucked with modpost at all so I don't have a good feel for
> what it does, or why we want to run it.
> 
> My quick skimming says modpost is all about generating the module
> version symbol scrambling.  Which if that is all it does means it is
> senseless to run this without modules.

Recently modpost has been enhanced to do section reference checks.
So modpost is used to check that there is no references from .text to
.init.text - the latter will be freed by the kernel so we better avoid
it.

The consistency checks does a bit more than just that simple check but
this was enough reason to run it twice in the build process.

	Sam

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  8:32 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 [this message]
2006-08-09  1:32   ` Magnus Damm
2006-08-09  6:29     ` Sam Ravnborg
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=20060808220509.GA8378@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

Powered by JetHome