From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH] kernel/cpu.c: Section mismatch warning fix. Date: Tue, 4 Nov 2008 10:48:31 +0100 Message-ID: <20081104094831.GP23790@elte.hu> References: <20081103153425.7282ab84.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:39879 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751763AbYKDJsj (ORCPT ); Tue, 4 Nov 2008 04:48:39 -0500 Content-Disposition: inline In-Reply-To: <20081103153425.7282ab84.akpm@linux-foundation.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andrew Morton Cc: Rakib Mullick , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org * Andrew Morton wrote: > On Thu, 30 Oct 2008 10:04:54 +0600 > "Rakib Mullick" wrote: > > > LD kernel/built-in.o > > WARNING: kernel/built-in.o(.text+0xb7c8): Section mismatch in > > reference from the function notify_cpu_starting() to the variable > > .cpuinit.data:cpu_chain > > The function notify_cpu_starting() references > > the variable __cpuinitdata cpu_chain. > > This is often because notify_cpu_starting lacks a __cpuinitdata > > annotation or the annotation of cpu_chain is wrong. > > > > This patch fixes the above section mismatch warning. If anything else > > please notice. > > Thanks. > > > > Signed-off-by: Md.Rakib H. Mullick > > > > --- linux-2.6-orig/kernel/cpu.c 2008-10-28 20:52:38.000000000 +0600 > > +++ linux-2.6/kernel/cpu.c 2008-10-28 22:46:22.000000000 +0600 > > @@ -462,7 +462,7 @@ out: > > * It must be called by the arch code on the new cpu, before the new cpu > > * enables interrupts and before the "boot" cpu returns from __cpu_up(). > > */ > > -void notify_cpu_starting(unsigned int cpu) > > +void __cpuinit notify_cpu_starting(unsigned int cpu) > > { > > unsigned long val = CPU_STARTING; > > arch/alpha/kernel/smp.c calls notify_cpu_starting() from __init code. > > arch/cris/arch-v32/kernel/smp.c calls notify_cpu_starting() from __init code. > > arch/x86/mach-voyager/voyager_smp.c calls notify_cpu_starting() from > __init code. > > arch/m32r/kernel/smpboot.c calls notify_cpu_starting() from __init code. > > arch/sparc/kernel/sun4d_smp.c calls notify_cpu_starting() from __init code. > > arch/powerpc/kernel/smp.c calls notify_cpu_starting() from __devinit > code. > > arch/um/kernel/smp.c calls notify_cpu_starting() from .text code. > > > The other nine callers call notify_cpu_starting() from __cpuinit code. > > > What a mess. __cpuinit seems safe for all but UML. But even for UML it appears to be de-facto safe: as after bootup we never return back into arch/um/kernel/smp.c::idle_proc(). (as UML's default_idle() is an infinite loop) Yesterday i've queued it up in tip/core/urgent: 685aebb: kernel/cpu.c: section mismatch warning fix to be pushed to Linus today-ish. Any objections? Ingo