From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 1/2] fix kill_proc_info() vs CLONE_THREAD race
Date: Thu, 16 Feb 2006 11:19:32 -0800 [thread overview]
Message-ID: <20060216191932.GE1296@us.ibm.com> (raw)
In-Reply-To: <43F37D54.4D0AAEFD@tv-sign.ru>
On Wed, Feb 15, 2006 at 10:13:24PM +0300, Oleg Nesterov wrote:
> There is a window after copy_process() unlocks ->sighand.siglock
> and before it adds the new thread to the thread list.
>
> In that window __group_complete_signal(SIGKILL) will not see the
> new thread yet, so this thread will start running while the whole
> thread group was supposed to exit.
The fix looks good to me!
> I beleive we have another good reason to place attach_pid(PID/TGID)
> under ->sighand.siglock. We can do the same for
>
> release_task()->__unhash_process()
>
> de_thread()->switch_exec_pids()
>
> After that we don't need tasklist_lock to iterate over the thread
> list, and we can simplify things, see for example do_sigaction()
> or sys_times().
The above proposal would require that we hold siglock during the
traversal, correct? Is that reasonable for non-signal-related traversals?
Or were you thinking of making this change only for signal code?
Thanx, Paul
Acked-by: <paulmck@us.ibm.com>
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
>
> --- 2.6.16-rc3/kernel/fork.c~1_KILL 2006-02-15 22:52:07.000000000 +0300
> +++ 2.6.16-rc3/kernel/fork.c 2006-02-15 23:21:51.000000000 +0300
> @@ -1123,8 +1123,8 @@ static task_t *copy_process(unsigned lon
> p->real_parent = current;
> p->parent = p->real_parent;
>
> + spin_lock(¤t->sighand->siglock);
> 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
> @@ -1162,8 +1162,6 @@ static task_t *copy_process(unsigned lon
> */
> p->it_prof_expires = jiffies_to_cputime(1);
> }
> -
> - spin_unlock(¤t->sighand->siglock);
> }
>
> /*
> @@ -1189,6 +1187,7 @@ static task_t *copy_process(unsigned lon
>
> nr_threads++;
> total_forks++;
> + spin_unlock(¤t->sighand->siglock);
> write_unlock_irq(&tasklist_lock);
> proc_fork_connector(p);
> return p;
>
next prev parent reply other threads:[~2006-02-16 19:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:45 [PATCH] fix kill_proc_info() vs copy_process() race Oleg Nesterov
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 [this message]
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=20060216191932.GE1296@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--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