mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: bugme-daemon@bugzilla.kernel.org, lkml <linux-kernel@vger.kernel.org>
Cc: wbrana@gmail.com
Subject: Re: [Bug 8679] New: Section mismatch: reference to .init.text
Date: Tue, 26 Jun 2007 12:01:34 -0700	[thread overview]
Message-ID: <20070626120134.17aa6143.randy.dunlap@oracle.com> (raw)
In-Reply-To: <bug-8679-10286@http.bugzilla.kernel.org/>

On Tue, 26 Jun 2007 10:46:36 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8679
> 
>            Summary: Section mismatch: reference to .init.text
>            Product: Other
>            Version: 2.5
>      KernelVersion: 2.6.22-rc6
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Configuration
>         AssignedTo: zippel@linux-m68k.org
>         ReportedBy: wbrana@gmail.com
> 
> 
> Software Environment:
> gcc 3.4.6, binutils 2.17
> 
> Problem Description:
> Warnings appeared while building kernel:
> 
> WARNING: arch/i386/kernel/built-in.o(.data+0x2148): Section mismatch: reference
> to .init.text: (between 'thermal_throttle_cpu_notifier' and 'mtrr_mutex')
> WARNING: kernel/built-in.o(.text+0x15f84): Section mismatch: reference to
> .init.text: (between 'kthreadd' and 'init_waitqueue_head')


I don't see the kernel/built-in.o warning when I build this (I have
binutils 2.16++).  Can you test the patch below to verify that it
fixes the warning?

On the other warning ('thermal_throttle_cpu_notifier'), we have:

static struct notifier_block thermal_throttle_cpu_notifier =
{
	.notifier_call = thermal_throttle_cpu_callback,
};

where CONFIG_CPU_HOTPLUG=n, so __cpuinit == __init in:

static __cpuinit int thermal_throttle_cpu_callback(struct notifier_block *nfb,
						   unsigned long action,
						   void *hcpu)


so CPU hotplug actions should never happen here.  Still, we have
a registered notifier that is in __init space and has been discarded... :(
Any suggestions out there?



---
From: Randy Dunlap <randy.dunlap@oracle.com>

kthreadd_setup() is in an __init section, but we know that it's
safe to be called from kthreadd() since the latter is only called
at kernel init time, so mark kthreadd_setup() __init_refok so
that modpost won't complain about what text section it is in.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 kernel/kthread.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6.22-rc6.orig/kernel/kthread.c
+++ linux-2.6.22-rc6/kernel/kthread.c
@@ -215,7 +215,7 @@ int kthread_stop(struct task_struct *k)
 EXPORT_SYMBOL(kthread_stop);
 
 
-static __init void kthreadd_setup(void)
+static __init_refok void kthreadd_setup(void)
 {
 	struct task_struct *tsk = current;
 

       reply	other threads:[~2007-06-26 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8679-10286@http.bugzilla.kernel.org/>
2007-06-26 19:01 ` Randy Dunlap [this message]
2007-06-26 21:32   ` Satyam Sharma
2007-06-26 21:42     ` Satyam Sharma

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=20070626120134.17aa6143.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wbrana@gmail.com \
    /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

all inboxes | Powered by JetHome®