Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754170AbaBRX0F (ORCPT ); Tue, 18 Feb 2014 18:26:05 -0500 Received: from mail-qa0-f43.google.com ([209.85.216.43]:34409 "EHLO mail-qa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753373AbaBRX0B (ORCPT ); Tue, 18 Feb 2014 18:26:01 -0500 Date: Tue, 18 Feb 2014 18:25:56 -0500 From: Tejun Heo To: Li Zefan Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH cgroup/for-3.14-fixes] cgroup: update cgroup_enable_task_cg_lists() to grab siglock Message-ID: <20140218232556.GM31892@mtj.dyndns.org> References: <20140213182931.GB17608@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140213182931.GB17608@htj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 13, 2014 at 01:29:31PM -0500, Tejun Heo wrote: > Currently, there's nothing preventing cgroup_enable_task_cg_lists() > from missing set PF_EXITING and race against cgroup_exit(). Depending > on the timing, cgroup_exit() may finish with the task still linked on > css_set leading to list corruption. Fix it by grabbing siglock in > cgroup_enable_task_cg_lists() so that PF_EXITING is guaranteed to be > visible. > > This whole on-demand cg_list optimization is extremely fragile and has > ample possibility to lead to bugs which can cause things like > once-a-year oops during boot. I'm wondering whether the better > approach would be just adding "cgroup_disable=all" handling which > disables the whole cgroup rather than tempting fate with this > on-demand craziness. > > Signed-off-by: Tejun Heo > Cc: stable@vger.kernel.org Applied to cgroup/for-3.14-fixes. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/