public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rmk+lkml@arm.linux.org.uk
Cc: cw@f00f.org, linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: (hacky) [PATCH] silence MODPOST section mismatch warnings
Date: Thu, 10 May 2007 14:07:25 -0700 (PDT)	[thread overview]
Message-ID: <20070510.140725.99616053.davem@davemloft.net> (raw)
In-Reply-To: <20070510205427.GF29713@flint.arm.linux.org.uk>

From: Russell King <rmk+lkml@arm.linux.org.uk>
Date: Thu, 10 May 2007 21:54:27 +0100

> I've not had one accurate one on ARM yet.
> 
> Here's another example:
> 
> WARNING: init/built-in.o - Section mismatch: reference to .init.text:
>  from .text between 'rest_init' (at offset 0x4c) and 'run_init_process'
> 
> from init/main.c:
> 
> static void noinline rest_init(void)
>         __releases(kernel_lock)
> 
> static void run_init_process(char *init_filename)
> 
> Clearly, it just does _not_ work.

Russell, the symbols are where the reference to an .init.text
section are coming from, they are not the .init.text function
being referenced itself.

It is saying that something between rest_init and run_init_processes,
which are not .init.text, are referencing an .init.text object.

It's unfortunate that the .init.text object being referenced for some
reason can't get the symbol printed out properly on ARM, it does get
printed out on other platforms, but once you fix that it will be very
easy for you to decode these messages.

But they are still useful.

The other one you posted was legitimate and as I explained just
needs an exception entry added to modpost.c

  parent reply	other threads:[~2007-05-10 21:07 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
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 [this message]
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=20070510.140725.99616053.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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