public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ilya Loginov <isloginov@gmail.com>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH] init: Fix race between init and kthreadd -v3
Date: Mon, 28 Jun 2010 16:51:01 +0200	[thread overview]
Message-ID: <1277736661.3561.110.camel@laptop> (raw)
In-Reply-To: <20100628141927.GA9306@elte.hu>

On Mon, 2010-06-28 at 16:19 +0200, Ingo Molnar wrote:

> I think you may be using a mutex as a completion in essence. Why not use 
> completions instead?

Totally forgot about those things.. Yes they fit perfectly.

---
Subject: init: Fix race between init and kthreadd -v2

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>
---
 init/main.c |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/init/main.c b/init/main.c
index e2a2bf3..2280f63 100644
--- a/init/main.c
+++ b/init/main.c
@@ -420,18 +420,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();
 
 	/*
@@ -847,6 +855,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();
 
 	/*


  reply	other threads:[~2010-06-28 14:51 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           ` Peter Zijlstra [this message]
2010-06-28 15:03             ` [PATCH] init: Fix race between init and kthreadd -v3 Linus Torvalds
2010-06-28 16:23             ` Randy Dunlap
2010-06-28 20:24             ` [tip:sched/urgent] init, sched: Fix race between init and kthreadd tip-bot for Peter Zijlstra
2010-06-30  8:32             ` [PATCH] init: Fix race between init and kthreadd -v3 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=1277736661.3561.110.camel@laptop \
    --to=peterz@infradead.org \
    --cc=isloginov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox