From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Roland McGrath <roland@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm 2/2] is_current_single_threaded: don't use ->mmap_sem
Date: Thu, 9 Jul 2009 23:28:49 +0200 [thread overview]
Message-ID: <20090709212849.GA10245@redhat.com> (raw)
is_current_single_threaded() can safely miss a freshly forked CLONE_VM
task, but in this case it must not miss its parent. That is why we take
mm->mmap_sem for writing to make sure a thread/task with the same ->mm
can't pass exit_mm() and disappear.
However we can avoid ->mmap_sem and rely on rcu/barriers:
- if we do not see the exiting parent on thread/process list
we see the result of list_del_rcu(), in this case we must
also see the result of list_add_rcu() which does wmb().
- if we do see the parent but its ->mm == NULL, we need rmb()
to make sure we can't miss the child.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
lib/is_single_threaded.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--- WAIT/lib/is_single_threaded.c~ISS_2_RCU 2009-07-09 22:16:29.000000000 +0200
+++ WAIT/lib/is_single_threaded.c 2009-07-09 22:54:41.000000000 +0200
@@ -22,8 +22,6 @@ bool is_current_single_threaded(void)
struct task_struct *p, *t;
bool ret;
- might_sleep();
-
if (atomic_read(&task->signal->live) != 1)
return false;
@@ -31,7 +29,6 @@ bool is_current_single_threaded(void)
return true;
ret = false;
- down_write(&mm->mmap_sem);
rcu_read_lock();
for_each_process(p) {
if (unlikely(p->flags & PF_KTHREAD))
@@ -45,12 +42,17 @@ bool is_current_single_threaded(void)
goto found;
if (likely(t->mm))
break;
+ /*
+ * t->mm == NULL. Make sure next_thread/next_task
+ * will see other CLONE_VM tasks which might be
+ * forked before exiting.
+ */
+ smp_rmb();
} while_each_thread(p, t);
}
ret = true;
found:
rcu_read_unlock();
- up_write(&mm->mmap_sem);
return ret;
}
next reply other threads:[~2009-07-09 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:28 Oleg Nesterov [this message]
2009-07-09 21:33 ` [PATCH -mm 2/2] is_current_single_threaded: don't use ->mmap_sem 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=20090709212849.GA10245@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=paulmck@linux.vnet.ibm.com \
--cc=roland@redhat.com \
--cc=sds@tycho.nsa.gov \
/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.