mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Bogus section mismatch errors?
Date: Wed, 9 May 2007 18:59:54 +0900	[thread overview]
Message-ID: <20070509095954.GA21844@linux-sh.org> (raw)
In-Reply-To: <20070508115220.GA29160@uranus.ravnborg.org>

On Tue, May 08, 2007 at 01:52:20PM +0200, Sam Ravnborg wrote:
> On Tue, May 08, 2007 at 12:17:59PM +0100, Russell King wrote:
> > WARNING: mm/built-in.o - Section mismatch:
> >  reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1bd94)
> >  and 'cache_reap'
> > WARNING: mm/built-in.o - Section mismatch:
> >  reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1bdcc)
> >  and 'cache_reap'
> There are in slab a function that is not marked __init that refer to a function marked
> __init. But the logic surrounding makes it OK.
> 
> I have no fix/workaround for this.
> Andres has suggested that we should mark functions/data that may refer to __init{data}
> with something like: __nowarn and __nowarndata
> 
Here's one I've started getting with the quicklist changes:

WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1ba5c) and 'quicklist_total_size'

quicklist_total_size() is not marked __init, nor is show_mem() in
arch/sh/mm/init.c, where I've added the reference. Ideas?

      parent reply	other threads:[~2007-05-09 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 11:17 Russell King
2007-05-08 11:52 ` Sam Ravnborg
2007-05-08 20:41   ` David Miller
2007-05-09  9:59   ` Paul Mundt [this message]

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=20070509095954.GA21844@linux-sh.org \
    --to=lethal@linux-sh.org \
    --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

Powered by JetHome