From: Oleg Nesterov <oleg@redhat.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
paulmck@linux.vnet.ibm.com,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Update comment on find_task_by_pid_ns
Date: Mon, 8 Feb 2010 14:21:01 +0100 [thread overview]
Message-ID: <20100208132101.GA7129@redhat.com> (raw)
In-Reply-To: <201002082130.JDC57339.OHOVJFQtFSLFMO@I-love.SAKURA.ne.jp>
On 02/08, Tetsuo Handa wrote:
>
> [PATCH] Update comment on find_task_by_pid_ns
>
> Caller of find_task_by_vpid() and find_task_by_pid_ns() needs to call
> rcu_read_lock() rather than read_lock(&tasklist_lock) because find_pid_ns()
> uses RCU primitives but spinlock does not prevent RCU callback if preemptive
> RCU ( CONFIG_TREE_PREEMPT_RCU ) is enabled.
I agree with the patch, but the changelog looks a bit confusing to me.
Perhaps this is just me, though.
tasklist does protect the task and its pid, it can't go away. The problem
is that find_pid_ns() itself is unsafe without rcu lock, it can race with
copy_process()->free_pid(any_pid).
IOW, if we change copy_process()
--- kernel/fork.c
+++ kernel/fork.c
@@ -1304,8 +1304,11 @@ static struct task_struct *copy_process(
return p;
bad_fork_free_pid:
- if (pid != &init_struct_pid)
+ if (pid != &init_struct_pid) {
+ read_lock(&tasklist_lock);
free_pid(pid);
+ read_unlock(&tasklist_lock);
+ }
bad_fork_cleanup_io:
if (p->io_context)
exit_io_context(p);
then find_task_by_pid_ns/etc could be used under tasklist safely even
with PREEMPT_RCU.
In any case, I think the patch is nice.
Oleg.
next prev parent reply other threads:[~2010-02-08 13:21 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 0:52 [patch 0/9] Fix various __task_cred related invalid RCU assumptions Thomas Gleixner
2009-12-10 0:52 ` [patch 1/9] sys: Fix missing rcu protection for __task_cred() access Thomas Gleixner
2009-12-10 1:25 ` Paul E. McKenney
2009-12-10 2:29 ` Tetsuo Handa
2009-12-10 2:43 ` Paul E. McKenney
2009-12-10 14:29 ` Oleg Nesterov
2009-12-10 14:44 ` Thomas Gleixner
2009-12-11 13:45 ` David Howells
2009-12-11 13:52 ` Thomas Gleixner
2009-12-10 14:20 ` Oleg Nesterov
2009-12-10 14:38 ` Thomas Gleixner
2009-12-10 15:08 ` [patch 1/9] sys: Fix missing rcu protection for __task_cred()access Tetsuo Handa
2009-12-10 21:17 ` Thomas Gleixner
2009-12-11 3:25 ` Tetsuo Handa
2010-02-08 12:30 ` [PATCH] Update comment on find_task_by_pid_ns Tetsuo Handa
2010-02-08 13:21 ` Oleg Nesterov [this message]
2010-02-08 17:07 ` Thomas Gleixner
2010-02-08 17:16 ` Oleg Nesterov
2010-02-08 21:42 ` Tetsuo Handa
2010-02-09 22:08 ` Andrew Morton
2010-02-10 16:30 ` Serge E. Hallyn
2010-02-10 17:57 ` Andrew Morton
2010-02-10 18:39 ` Thomas Gleixner
2010-02-10 20:18 ` Serge E. Hallyn
2010-02-10 20:30 ` Paul E. McKenney
2010-02-11 1:21 ` Tetsuo Handa
2010-02-11 12:04 ` [PATCH] sys: Fix missing rcu protection for sys_getpriority Tetsuo Handa
2010-02-12 14:22 ` Serge E. Hallyn
2009-12-10 22:09 ` [tip:core/urgent] sys: Fix missing rcu protection for __task_cred() access tip-bot for Thomas Gleixner
2009-12-11 13:41 ` [patch 1/9] " David Howells
2009-12-10 0:52 ` [patch 2/9] fs: Add missing rcu protection for __task_cred() in sys_ioprio_get Thomas Gleixner
2009-12-11 13:46 ` David Howells
2009-12-10 0:53 ` [patch 3/9] proc: Add missing rcu protection for __task_cred() in task_sig() Thomas Gleixner
2009-12-11 13:46 ` David Howells
2009-12-10 0:53 ` [patch 4/9] oom: Add missing rcu protection of __task_cred() in dump_tasks Thomas Gleixner
2009-12-10 1:57 ` KOSAKI Motohiro
2009-12-11 13:49 ` David Howells
2009-12-11 13:52 ` Thomas Gleixner
2009-12-10 0:53 ` [patch 5/9] security: Use get_task_cred() in keyctl_session_to_parent() Thomas Gleixner
2009-12-10 2:45 ` Paul E. McKenney
2009-12-11 13:52 ` David Howells
2009-12-10 0:53 ` [patch 6/9] signal: Fix racy access to __task_cred in kill_pid_info_as_uid() Thomas Gleixner
2009-12-10 15:11 ` Oleg Nesterov
2009-12-10 22:09 ` [tip:core/urgent] " tip-bot for Thomas Gleixner
2009-12-11 13:53 ` [patch 6/9] " David Howells
2009-12-10 0:53 ` [patch 7/9] signals: Fix more rcu assumptions Thomas Gleixner
2009-12-10 14:34 ` Oleg Nesterov
2009-12-10 14:45 ` Thomas Gleixner
2009-12-11 13:59 ` David Howells
2009-12-10 22:09 ` [tip:core/urgent] " tip-bot for Thomas Gleixner
2009-12-10 0:53 ` [patch 8/9] Documentation: Fix invalid " Thomas Gleixner
2009-12-10 23:55 ` Vegard Nossum
2009-12-11 14:00 ` David Howells
2009-12-11 16:07 ` Linus Torvalds
2009-12-11 16:37 ` Paul E. McKenney
2009-12-11 18:08 ` Thomas Gleixner
2009-12-11 21:28 ` Arnd Bergmann
2009-12-11 22:01 ` Paul E. McKenney
2009-12-10 0:53 ` [patch 9/9] security: Fix invalid rcu assumptions in comments Thomas Gleixner
2009-12-11 14:01 ` David Howells
2009-12-10 2:28 ` [patch 0/9] Fix various __task_cred related invalid RCU assumptions Paul E. McKenney
2009-12-10 3:15 ` Linus Torvalds
2009-12-10 5:13 ` Peter Zijlstra
2009-12-10 5:34 ` Paul E. McKenney
2009-12-13 18:56 ` Peter Zijlstra
2009-12-14 1:53 ` Paul E. McKenney
2009-12-14 10:17 ` Peter Zijlstra
2009-12-14 14:16 ` Paul E. McKenney
2009-12-14 14:30 ` Peter Zijlstra
2009-12-15 1:23 ` Paul E. McKenney
2009-12-11 13:39 ` David Howells
2009-12-11 16:35 ` 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=20100208132101.GA7129@redhat.com \
--to=oleg@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tglx@linutronix.de \
/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