From: Oleg Nesterov <oleg@tv-sign.ru>
To: Ingo Molnar <mingo@elte.hu>, "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: [PATCH] fix kill_proc_info() vs copy_process() race
Date: Mon, 06 Feb 2006 19:45:48 +0300 [thread overview]
Message-ID: <43E77D3C.C967A275@tv-sign.ru> (raw)
kill_proc_info() takes taskllist_lock only for sig_kernel_stop()
case nowadays. I beleive it races with copy_process().
The first race is simple, copy_process:
/*
* Check for pending SIGKILL! The new thread should not be allowed
* to slip out of an OOM kill. (or normal SIGKILL.)
*/
if (sigismember(¤t->pending.signal, SIGKILL))
return EINTR;
This relies on tasklist_lock and is racy now.
The second race is more tricky, copy_process:
attach_pid(p, PIDTYPE_PID, p->pid);
attach_pid(p, PIDTYPE_TGID, p->tgid);
This means that we can find a task in kill_proc_info()->find_task_by_pid()
which is not registered as part of thread group yet. Various bad things can
happen, note that handle_stop_signal(SIGCONT) and __group_complete_signal()
iterate over threads list. But p->pids[PIDTYPE_TGID] is a copy of current's
'struct pid' from dup_task_struct(), and if we don't have CLONE_THREAD here
we will use completely unreleated (parent's) thread list.
I think we can solve these problems by enlarging a ->siglock's scope in
copy_process(), but I don't know how to test this patch.
NOTE: release_task()->__unhash_process() path is safe, we already have
->sighand == NULL while detaching PIDTYPE_PID/PIDTYPE_TGID nonatomically.
Unless I missed something, I personally think this is a 2.6.16 material.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
--- RC-1/kernel/fork.c~ 2006-02-06 22:04:40.000000000 +0300
+++ RC-1/kernel/fork.c 2006-02-06 22:11:51.000000000 +0300
@@ -1050,7 +1050,7 @@ static task_t *copy_process(unsigned lon
sched_fork(p, clone_flags);
/* Need tasklist lock for parent etc handling! */
- write_lock_irq(&tasklist_lock);
+ write_lock(&tasklist_lock);
/*
* The task hasn't been attached yet, so its cpus_allowed mask will
@@ -1066,33 +1066,34 @@ static task_t *copy_process(unsigned lon
!cpu_online(task_cpu(p))))
set_task_cpu(p, smp_processor_id());
+ /* CLONE_PARENT re-uses the old parent */
+ if (clone_flags & (CLONE_PARENT|CLONE_THREAD))
+ p->real_parent = current->real_parent;
+ else
+ p->real_parent = current;
+ p->parent = p->real_parent;
+
+ spin_lock_irq(¤t->sighand->siglock);
/*
* Check for pending SIGKILL! The new thread should not be allowed
* to slip out of an OOM kill. (or normal SIGKILL.)
*/
if (sigismember(¤t->pending.signal, SIGKILL)) {
- write_unlock_irq(&tasklist_lock);
+ spin_unlock_irq(¤t->sighand->siglock);
+ write_unlock(&tasklist_lock);
retval = -EINTR;
goto bad_fork_cleanup_namespace;
}
- /* CLONE_PARENT re-uses the old parent */
- if (clone_flags & (CLONE_PARENT|CLONE_THREAD))
- p->real_parent = current->real_parent;
- else
- p->real_parent = current;
- p->parent = p->real_parent;
-
if (clone_flags & CLONE_THREAD) {
- spin_lock(¤t->sighand->siglock);
/*
* Important: if an exit-all has been started then
* do not create this new thread - the whole thread
* group is supposed to exit anyway.
*/
if (current->signal->flags & SIGNAL_GROUP_EXIT) {
- spin_unlock(¤t->sighand->siglock);
- write_unlock_irq(&tasklist_lock);
+ spin_unlock_irq(¤t->sighand->siglock);
+ write_unlock(&tasklist_lock);
retval = -EAGAIN;
goto bad_fork_cleanup_namespace;
}
@@ -1122,8 +1123,6 @@ static task_t *copy_process(unsigned lon
*/
p->it_prof_expires = jiffies_to_cputime(1);
}
-
- spin_unlock(¤t->sighand->siglock);
}
/*
@@ -1151,7 +1150,9 @@ static task_t *copy_process(unsigned lon
nr_threads++;
total_forks++;
- write_unlock_irq(&tasklist_lock);
+ spin_unlock_irq(¤t->sighand->siglock);
+ write_unlock(&tasklist_lock);
+
proc_fork_connector(p);
return p;
next reply other threads:[~2006-02-06 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:45 Oleg Nesterov [this message]
2006-02-06 17:10 ` Oleg Nesterov
2006-02-06 20:25 ` Oleg Nesterov
2006-02-14 22:32 ` Paul E. McKenney
2006-02-15 14:05 ` Oleg Nesterov
2006-02-15 19:13 ` [PATCH 1/2] fix kill_proc_info() vs CLONE_THREAD race Oleg Nesterov
2006-02-16 19:19 ` Paul E. McKenney
2006-02-16 21:16 ` Oleg Nesterov
2006-02-15 19:13 ` [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race Oleg Nesterov
2006-02-16 19:26 ` Paul E. McKenney
2006-02-16 20:56 ` Oleg Nesterov
2006-02-16 19:53 ` Paul E. McKenney
2006-02-16 21:20 ` Oleg Nesterov
2006-02-18 2:06 ` Paul E. McKenney
2006-02-18 18:19 ` Oleg Nesterov
2006-02-20 17:49 ` Paul E. McKenney
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=43E77D3C.C967A275@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®