From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, David Rientjes <rientjes@google.com>,
Pavel Emelianov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC][-mm] Memory controller add mm->owner
Date: Mon, 24 Mar 2008 09:34:39 -0700 [thread overview]
Message-ID: <6599ad830803240934g2a70d904m1ca5548f8644c906@mail.gmail.com> (raw)
In-Reply-To: <47E7D51E.4050304@linux.vnet.ibm.com>
On Mon, Mar 24, 2008 at 9:21 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > Also, if mm->owner exits but mm is still alive (unlikely, but could
> > happen with weird custom threading libraries?) then we need to
> > reassign mm->owner to one of the other users of the mm (by looking
> > first in the thread group, then among the parents/siblings/children,
> > and then among all processes as a last resort?)
> >
>
> The comment in __exit_signal states that
>
> "The group leader stays around as a zombie as long
> as there are other threads. When it gets reaped,
> the exit.c code will add its counts into these totals."
Ah, that's useful to know.
>
> Given that the thread group leader stays around, do we need to reassign
> mm->owner? Do you do anything special in cgroups like cleanup the
> task_struct->css->subsys_state on exit?
>
OK, so we don't need to handle this for NPTL apps - but for anything
still using LinuxThreads or manually constructed clone() calls that
use CLONE_VM without CLONE_PID, this could still be an issue. (Also I
guess there's the case of someone holding a reference to the mm via a
/proc file?)
>
> >> - rcu_read_lock();
> >> - mem = rcu_dereference(mm->mem_cgroup);
> >> + mem = mem_cgroup_from_task(mm->owner);
> >
> > I think we still need the rcu_read_lock(), since mm->owner can move
> > cgroups any time.
> >
>
> OK, so cgroup task movement is protected by RCU, right? I'll check for all
> mm->owner uses.
>
Yes - cgroup_attach() uses synchronize_rcu() before release the cgroup
mutex. So although you can't guarantee that the cgroup set won't
change if you're just using RCU, you can't guarantee that you're
addressing a still-valid non-destroyed (and of course non-freed)
cgroup set.
Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-03-24 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 14:01 Balbir Singh
2008-03-24 15:03 ` Paul Menage
2008-03-24 16:21 ` Balbir Singh
2008-03-24 16:34 ` Paul Menage [this message]
2008-03-24 17:33 ` Balbir Singh
2008-03-24 17:46 ` Paul Menage
2008-03-25 11:41 ` Balbir Singh
2008-03-26 10:29 ` Balbir Singh
2008-03-26 11:20 ` Paul Menage
2008-03-26 11:41 ` Balbir Singh
2008-03-26 15:21 ` Paul Menage
2008-03-25 1:26 ` Li Zefan
2008-03-25 15:48 ` Balbir Singh
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=6599ad830803240934g2a70d904m1ca5548f8644c906@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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