From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kosaki.motohiro@jp.fujitsu.com, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
tglx <tglx@linutronix.de>, Oleg Nesterov <oleg@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: rcu_read_lock/unlock protect find_task_by_vpid call in migrate_pages
Date: Thu, 25 Nov 2010 18:59:58 +0900 (JST) [thread overview]
Message-ID: <20101125174751.F45C.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1290674541.2072.564.camel@laptop>
> On Thu, 2010-11-25 at 09:50 +0900, KOSAKI Motohiro wrote:
> > Hi
> >
> > > Signed-off-by: Dave Jones <davej@redhat.com>
> > >
> > > diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> > > index 4a57f13..2f0f55b 100644
> > > --- a/mm/mempolicy.c
> > > +++ b/mm/mempolicy.c
> > > @@ -1308,6 +1308,7 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
> > >
> > > /* Find the mm_struct */
> > > read_lock(&tasklist_lock);
> > > + rcu_read_lock();
> > > task = pid ? find_task_by_vpid(pid) : current;
> > > if (!task) {
> > > read_unlock(&tasklist_lock);
> > > @@ -1315,6 +1316,7 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
> > > goto out;
> > > }
> > > mm = get_task_mm(task);
> > > + rcu_read_unlock();
> > > read_unlock(&tasklist_lock);
> > >
> > > err = -EINVAL;
> >
> > Thanks reporting. but mmotm seems already has the same patch.
>
> Another one,... again:
>
>
> Do we still need the tasklist_lock in this case?
>
> Also, why is that think complaining, surely the tasklist_lock pins any
> and all PID objects?
(cc to Christoph and Oleg)
Good spotting.
As far as I understand, find_task_by_pid() did required tasklist_lock in
old days. but It isn't now.
So I think we can remove tasklist_lock from here.
===========================================================================
>From 9de9f70f74e55d92b5e9057e22fc629405f63295 Mon Sep 17 00:00:00 2001
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Date: Thu, 16 Dec 2010 17:49:23 +0900
Subject: [PATCH] mempolicy: remove tasklist_lock from migrate_pages
Today, tasklist_lock in migrate_pages doesn't protect anything.
rcu_read_lock() provide enough protection from pid hash walk.
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
---
mm/mempolicy.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index 11ff260..9064945 100644
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -1308,16 +1308,13 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
/* Find the mm_struct */
rcu_read_lock();
- read_lock(&tasklist_lock);
task = pid ? find_task_by_vpid(pid) : current;
if (!task) {
- read_unlock(&tasklist_lock);
rcu_read_unlock();
err = -ESRCH;
goto out;
}
mm = get_task_mm(task);
- read_unlock(&tasklist_lock);
rcu_read_unlock();
err = -EINVAL;
--
1.6.5.2
prev parent reply other threads:[~2010-11-25 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 0:33 rcu_read_lock/unlock protect find_task_by_vpid call in migrate_pages Dave Jones
2010-11-25 0:50 ` KOSAKI Motohiro
2010-11-25 1:33 ` Dave Jones
2010-11-25 8:42 ` Peter Zijlstra
2010-11-25 9:59 ` KOSAKI Motohiro [this message]
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=20101125174751.F45C.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--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