linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Pavel Emelianov <xemul@openvz.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, linux-mm@kvack.org,
	David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v7)
Date: Thu, 03 Apr 2008 23:41:51 +0530	[thread overview]
Message-ID: <47F51DE7.7010204@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830804031058l1e2a7ad9p56cff47dca738d79@mail.gmail.com>

Paul Menage wrote:
> On Thu, Apr 3, 2008 at 10:44 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>>  +
>>  +       /*
>>  +        * If there are other users of the mm and the owner (us) is exiting
>>  +        * we need to find a new owner to take on the responsibility.
>>  +        * When we use thread groups (CLONE_THREAD), the thread group
>>  +        * leader is kept around in zombie state, even after it exits.
>>  +        * delay_group_leader() ensures that if the group leader is around
>>  +        * we need not select a new owner.
>>  +        */
> 
> Hmm, is this new check for delay_group_leader() safe? Won't we have
> called exit_cgroup() by this point, and hence be reassigned to the
> root cgroup? And so mm->owner->cgroups won't point to the right place?
> 

cgroup_exit() comes in much later after exit_mm(). Moreover delay_group_leader()
is a function that checks to see if

We are the group leader and the thread group is not empty.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2008-04-03 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 17:44 Balbir Singh
2008-04-03 17:58 ` Paul Menage
2008-04-03 18:11   ` Balbir Singh [this message]
2008-04-03 18:22     ` Paul Menage
2008-04-03 18:34       ` Balbir Singh
2008-04-03 18:41         ` Paul Menage
2008-04-03 18:48           ` Balbir Singh
2008-04-03 18:25 ` Dave Hansen
2008-04-03 18:30   ` Paul Menage
2008-04-03 18:51   ` Balbir Singh
2008-04-03 18:56     ` Paul Menage
2008-04-03 19:28       ` Balbir Singh
2008-04-03 18:59     ` Dave Hansen

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=47F51DE7.7010204@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --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=menage@google.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