From: Oleg Nesterov <oleg@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
James Morris <jmorris@namei.org>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rework/fix is_single_threaded()
Date: Thu, 16 Apr 2009 16:54:44 +0200 [thread overview]
Message-ID: <20090416145444.GA12884@redhat.com> (raw)
In-Reply-To: <20090416133658.GA6532@redhat.com>
On 04/16, Oleg Nesterov wrote:
>
> Suppose we have a process P which shares ->mm with "task" (the argument), so
> we should return "false".
>
> P does clone(CLONE_VM) and exits. rcu_read_lock() can't guarantee we will
> see the new task with the same ->mm. And without ->mmap_sem P can call
> exit_mm() and set P->mm = NULL.
>
> Hmm. But we can just add a barrier?
>
> bool is_single_threaded(struct task_struct *task)
> {
> struct mm_struct *mm = task->mm;
> struct task_struct *p, *t;
> bool ret;
>
> if (atomic_read(&task->signal->live) != 1)
> return false;
>
> if (atomic_read(&mm->mm_users) == 1)
> return true;
>
> ret = false;
> rcu_read_lock();
> for_each_process(p) {
> if (unlikely(p->flags & PF_KTHREAD))
> continue;
> if (unlikely(p == task->group_leader))
> continue;
>
> t = p;
> do {
> if (unlikely(t->mm == mm))
> goto found;
> if (likely(t->mm))
> break;
>
> /* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> t->mm == NULL. Perhaps it had the same ->mm ?
> If t has forked CLONE_VM task and called exit_mm(),
> make sure next_thread() or for_each_process()->next_task()
> will see it.
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> */
> smp_rmb();
Sorry, forgot to mention...
But what if P does clone(CLONE_VM), exits, and for_each_process/while_each_thread
doesn't see it? IOW, what if we already see the result of list_del_rcu() ?
I think, in that case we must also see the result of clone()->list_add_tail_rcu()
which has a barrier, so we are safe.
Hmm. I feel this all has a simpler explanation, or I missed something...
Oleg.
next prev parent reply other threads:[~2009-04-16 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 21:45 [PATCH] rework/fix is_single_threaded() Oleg Nesterov
2009-04-15 23:32 ` Andrew Morton
2009-04-16 13:40 ` Oleg Nesterov
2009-04-16 10:04 ` David Howells
2009-04-16 13:36 ` Oleg Nesterov
2009-04-16 14:36 ` Stephen Smalley
2009-04-16 14:54 ` Oleg Nesterov [this message]
2009-06-18 19:07 ` Andrew Morton
2009-06-18 19:42 ` Oleg Nesterov
2009-06-22 18:51 ` Andrew Morton
2009-06-22 17:14 ` Oleg Nesterov
2009-06-22 21:04 ` Andrew Morton
2009-06-22 19:24 ` Oleg Nesterov
2009-07-09 13:01 ` David Howells
2009-07-09 21:25 ` Oleg Nesterov
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=20090416145444.GA12884@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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