linux-kernel - Re: Section mismatch warnings (was Re: [PATCH] early_pfn_to_nid needs to be _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 May 2007 14:45:03 -0500
From:	linas@...tin.ibm.com (Linas Vepstas)
To:	Gabriel Paubert <paubert@...m.es>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	ppc-dev <linuxppc-dev@...abs.org>,
	Andrew Morton <akpm@...ux-foundation.org>, paulus@...ba.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Section mismatch warnings (was Re: [PATCH] early_pfn_to_nid needs to be __meminit)

On Wed, May 09, 2007 at 06:51:15PM +0200, Gabriel Paubert wrote:
> On Thu, May 10, 2007 at 02:25:52AM +1000, Stephen Rothwell wrote:
> > This removes a section mismatch warning in those circumstances.
> 
> Speaking of this, I just tried to compile an official (Linus' git tree) 
> kernel for my old PMac G4 and I get a lot of section mismatch warnings at 
> the end of the compilation:
> 
> WARNING: arch/powerpc/mm/built-in.o - Section mismatch: reference to .init.text:early_get_page from .text between 'pte_alloc_one_kernel' (at offset 0xf50) and 'v_mapped_by_bats'
> 
> I find these 50 or so warnings so scary that I've not yet tried 
> to boot the kernel. Note that this is a non-modular kernel.

I'm getting oodles of these on an older -mm2 tree. The kernels seem to
work fine. Yes, they should be fixed but I'm up to my proverbial eyballs
in alligators.

--linas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/