From: tip-bot for Peter Zijlstra <peterz@infradead.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
torvalds@linux-foundation.org, a.p.zijlstra@chello.nl,
peterz@infradead.org, isloginov@gmail.com, tglx@linutronix.de,
mingo@elte.hu
Subject: [tip:sched/urgent] init, sched: Fix race between init and kthreadd
Date: Mon, 28 Jun 2010 20:24:46 GMT [thread overview]
Message-ID: <tip-b433c3d4549ae74935b585115f076c6fb7bc48fe@git.kernel.org> (raw)
In-Reply-To: <1277736661.3561.110.camel@laptop>
Commit-ID: b433c3d4549ae74935b585115f076c6fb7bc48fe
Gitweb: http://git.kernel.org/tip/b433c3d4549ae74935b585115f076c6fb7bc48fe
Author: Peter Zijlstra <peterz@infradead.org>
AuthorDate: Mon, 28 Jun 2010 16:51:01 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 28 Jun 2010 18:21:30 +0200
init, sched: Fix race between init and kthreadd
Ilya reported that on a very slow machine he could reliably
reproduce a race between forking init and kthreadd. We first
fork init so that it obtains pid-1, however since the scheduler
is already fully running at this point it can preempt and run
the init thread before we spawn and set kthreadd_task.
The init thread can then attempt spawning kthreads without
kthreadd being present which results in an OOPS.
Reported-by: Ilya Loginov <isloginov@gmail.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
LKML-Reference: <1277736661.3561.110.camel@laptop>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
init/main.c | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/init/main.c b/init/main.c
index 3bdb152..633442f 100644
--- a/init/main.c
+++ b/init/main.c
@@ -422,18 +422,26 @@ static void __init setup_command_line(char *command_line)
* gcc-3.4 accidentally inlines this function, so use noinline.
*/
+static __initdata DECLARE_COMPLETION(kthreadd_done);
+
static noinline void __init_refok rest_init(void)
__releases(kernel_lock)
{
int pid;
rcu_scheduler_starting();
+ /*
+ * We need to spawn init first so that it obtains pid-1, however
+ * the init task will end up wanting to create kthreads, which, if
+ * we schedule it before we create kthreadd, will OOPS.
+ */
kernel_thread(kernel_init, NULL, CLONE_FS | CLONE_SIGHAND);
numa_default_policy();
pid = kernel_thread(kthreadd, NULL, CLONE_FS | CLONE_FILES);
rcu_read_lock();
kthreadd_task = find_task_by_pid_ns(pid, &init_pid_ns);
rcu_read_unlock();
+ complete(&kthreadd_done);
unlock_kernel();
/*
@@ -855,6 +863,10 @@ static noinline int init_post(void)
static int __init kernel_init(void * unused)
{
+ /*
+ * Wait until kthreadd is all set-up.
+ */
+ wait_for_completion(&kthreadd_done);
lock_kernel();
/*
next prev parent reply other threads:[~2010-06-28 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:11 [PATCH] fix problem with reschenduling in rest_init (2.6.35-rc3) Ilya Loginov
2010-06-24 13:11 ` Peter Zijlstra
2010-06-24 13:23 ` Ilya Loginov
2010-06-24 14:08 ` Илья Логинов
2010-06-28 9:01 ` [PATCH] init: Fix race between init and kthreadd Peter Zijlstra
2010-06-28 11:53 ` [PATCH] init: Fix race between init and kthreadd -v2 Peter Zijlstra
2010-06-28 14:19 ` Ingo Molnar
2010-06-28 14:51 ` [PATCH] init: Fix race between init and kthreadd -v3 Peter Zijlstra
2010-06-28 15:03 ` Linus Torvalds
2010-06-28 16:23 ` Randy Dunlap
2010-06-28 20:24 ` tip-bot for Peter Zijlstra [this message]
2010-06-30 8:32 ` Ilya Loginov
2010-06-30 8:37 ` [PATCH] init: Fix comment Peter Zijlstra
2010-06-30 8:45 ` [tip:sched/urgent] " tip-bot for Peter Zijlstra
2010-06-28 20:06 ` [PATCH] init: Fix race between init and kthreadd -v2 Ilya Loginov
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=tip-b433c3d4549ae74935b585115f076c6fb7bc48fe@git.kernel.org \
--to=peterz@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=isloginov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.