From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Zefan Subject: Re: [PATCH v2] cgroup: Remove task_lock() from cgroup_post_fork() Date: Tue, 27 Dec 2011 09:33:35 +0800 Message-ID: <4EF9206F.3090207@cn.fujitsu.com> References: <1324610723-30080-1-git-send-email-fweisbec@gmail.com> <20111223230013.GV17084@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111223230013.GV17084-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Tejun Heo Cc: Frederic Weisbecker , Containers , Oleg Nesterov , LKML , Mandeep Singh Baines , Cgroups , Andrew Morton , Paul Menage List-Id: containers.vger.kernel.org Tejun Heo wrote: > On Fri, Dec 23, 2011 at 04:25:23AM +0100, Frederic Weisbecker wrote: >> cgroup_post_fork() is protected between threadgroup_change_begin() >> and threadgroup_change_end() against concurrent changes of the >> child's css_set in cgroup_task_migrate(). Also the child can't >> exit and call cgroup_exit() at this stage, this means it's css_set >> can't be changed with init_css_set concurrently. >> >> For these reasons, we don't need to hold task_lock() on the child >> because it's css_set can only remain stable in this place. >> >> Let's remove the lock there. >> >> v2: Update comment to explain that we are safe against >> cgroup_exit() >> >> Signed-off-by: Frederic Weisbecker >> Cc: Li Zefan >> Cc: Tejun Heo >> Cc: Containers >> Cc: Cgroups >> Cc: KAMEZAWA Hiroyuki >> Cc: Oleg Nesterov >> Cc: Andrew Morton >> Cc: Paul Menage >> Cc: Mandeep Singh Baines > > Li, does this look good to you? > Acked-by: Li Zefan