public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	Andrew Morton <akpm@osdl.org>,
	jamagallon@ono.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ignore smp_locks section warnings from init/exit code
Date: Sun, 11 Jun 2006 19:25:58 -0400	[thread overview]
Message-ID: <20060611232558.GB20639@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060608183549.GB18815@mars.ravnborg.org>

On Thu, Jun 08, 2006 at 08:35:49PM +0200, Sam Ravnborg wrote:
> As for .bss this is a much more generic section - so for now this is not
> added. Can you explain why there is a reference to do_mount_root from
> .bss or is this a bug in modpost pointing out something wrong?

For me, the ld complaints are completely opaque.  Can you give me a
clue how you go about figuring out where the complaint is coming from?

This is what I get with UML/x86_64 with rc6-mm2:
	WARNING: vmlinux - Section mismatch: reference to .init.text:huft_free from .bss between 'stdout@@GLIBC_2.2.5' (at offset 0x6027b748) and 'completed.6111'

gdb tells me:
	(gdb) x/4xa 0x6027b748
	0x6027b748 <stdout@@GLIBC_2.2.5>:       0x0     0x0
	0x6027b758 <completed.6111+8>:  0x0     0x0

So, with stdout@@GLIBC_2.2.5 at 0x6027b748 and completed.6111 at
0x6027b750 - right next to each other - there would seem to be nothing
between them to reference anything.

In any case, with bss containing zero-initialized stuff, I don't see
how anything here can refer to anything anywhere else.

> With the above patch we are down to two section mismatch warnings for
> a defconfig build on x86_64.

I see one (the one quoted above).  Thanks for adding .plt - that made
the build much more pleasant.

				Jeff

  reply	other threads:[~2006-06-11 23:26 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36     ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54     ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  0:31       ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08  6:30         ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  7:26       ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:11   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08  3:19     ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13       ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06     ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Duncan Sands
2006-06-12 14:35       ` Ingo Molnar
2006-06-08 12:54     ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23     ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08  0:04       ` Randy.Dunlap
2006-06-08  2:11       ` Jeff Dike
2006-06-08  2:32         ` Randy.Dunlap
2006-06-08  4:21           ` Jeff Dike
2006-06-08  4:29             ` Randy.Dunlap
2006-06-08 15:44               ` Randy.Dunlap
2006-06-08 18:35         ` Sam Ravnborg
2006-06-11 23:25           ` Jeff Dike [this message]
2006-06-12  0:17             ` Randy.Dunlap
2006-06-12  2:29               ` Jeff Dike
2006-06-12  2:52                 ` Randy.Dunlap
2006-06-08  2:25     ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  2:46       ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08  5:43         ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  6:46       ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08  1:09     ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08  5:00 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-20 17:42   ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24     ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21  6:23     ` 2.6.17-rc6-mm1 Dave Jones
2006-06-21  8:15       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42         ` 2.6.17-rc6-mm1 Dave Jones

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=20060611232558.GB20639@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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