From: Randy Dunlap <randy.dunlap@oracle.com>
To: Satyam Sharma <ssatyam@cse.iitk.ac.in>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@tv-sign.ru>,
Eric W Biederman <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -rc7][resend] kthread: Silence bogus section mismatch warning
Date: Sat, 7 Jul 2007 12:05:52 -0700 [thread overview]
Message-ID: <20070707120552.95a9a6aa.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070707164722.1356.52206.sendpatchset@cselinux1.cse.iitk.ac.in>
On Sat, 07 Jul 2007 22:17:22 +0530 Satyam Sharma wrote:
> This:
>
> WARNING: kernel/built-in.o(.text+0x16910): Section mismatch:
> reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
>
> comes because kernel/kthread.c:kthreadd() is not __init but calls
> kthreadd_setup() which is __init. But this is ok, because kthreadd_setup()
> is only ever called at init time, and then kthreadd() proceeds into its
> "for (;;)" loop. We could mark kthreadd __init_refok, but kthreadd_setup()
> with just one callsite and 4 lines in it (it's been that small since
> 10ab825bdef8df51) doesn't need to be a separate function at all -- so let's
> just move those four lines at beginning of kthreadd() itself.
>
> Signed-off-by: Satyam Sharma <ssatyam@cse.iitk.ac.in>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>
> First discussed in http://lkml.org/lkml/2007/6/26/274,
> and I keep getting this with:
> ...
>
> kernel/kthread.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> ---
>
> diff -ruNp a/kernel/kthread.c b/kernel/kthread.c
> --- a/kernel/kthread.c 2007-06-26 06:33:08.000000000 +0530
> +++ b/kernel/kthread.c 2007-06-27 02:57:46.000000000 +0530
> @@ -214,23 +214,15 @@ int kthread_stop(struct task_struct *k)
> }
> EXPORT_SYMBOL(kthread_stop);
>
> -
> -static __init void kthreadd_setup(void)
> +int kthreadd(void *unused)
> {
> struct task_struct *tsk = current;
>
> + /* Setup a clean context for our children to inherit. */
> set_task_comm(tsk, "kthreadd");
> -
> ignore_signals(tsk);
> -
> set_user_nice(tsk, -5);
> set_cpus_allowed(tsk, CPU_MASK_ALL);
> -}
> -
> -int kthreadd(void *unused)
> -{
> - /* Setup a clean context for our children to inherit. */
> - kthreadd_setup();
>
> current->flags |= PF_NOFREEZE;
>
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-07-07 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 16:47 Satyam Sharma
2007-07-07 19:05 ` Randy Dunlap [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=20070707120552.95a9a6aa.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=ssatyam@cse.iitk.ac.in \
/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®