From: Peter Zijlstra <peterz@infradead.org>
To: Ilya Loginov <isloginov@gmail.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] init: Fix race between init and kthreadd -v2
Date: Mon, 28 Jun 2010 13:53:17 +0200 [thread overview]
Message-ID: <1277725997.3561.6.camel@laptop> (raw)
In-Reply-To: <1277715689.1875.1104.camel@laptop>
On Mon, 2010-06-28 at 11:01 +0200, Peter Zijlstra wrote:
> static int __init kernel_init(void * unused)
> {
> + /*
> + * Synchronize against setting kthreadd_task in rest_init().
> + * Using a mutex would have been a lot nicer, but since its a very
> + * rare race don't bother wasting the space overhead.
> + */
> + while (!kthreadd_task)
> + yield();
> +
> lock_kernel();
I just realized its all __init code so its all 'free' anyway, how about
the nicer version:
---
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.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
init/main.c | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/init/main.c b/init/main.c
index e2a2bf3..8f2acf5 100644
--- a/init/main.c
+++ b/init/main.c
@@ -420,18 +420,27 @@ static void __init setup_command_line(char *command_line)
* gcc-3.4 accidentally inlines this function, so use noinline.
*/
+static __initdata DEFINE_MUTEX(kthreadd_lock);
+
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.
+ */
+ mutex_lock(&kthreadd_lock);
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();
+ mutex_unlock(&kthreadd_lock);
unlock_kernel();
/*
@@ -847,6 +856,13 @@ static noinline int init_post(void)
static int __init kernel_init(void * unused)
{
+ /*
+ * We spawned this thread while holding this lock, ensure the
+ * locked section in rest_init() is complete before proceeding.
+ */
+ mutex_lock(&kthreadd_lock);
+ mutex_unlock(&kthreadd_lock);
+
lock_kernel();
/*
next prev parent reply other threads:[~2010-06-28 11:53 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 ` Peter Zijlstra [this message]
2010-06-28 14:19 ` [PATCH] init: Fix race between init and kthreadd -v2 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: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=1277725997.3561.6.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 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.