From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f199.google.com (mail-qk0-f199.google.com [209.85.220.199]) by kanga.kvack.org (Postfix) with ESMTP id E851E6B0006 for ; Mon, 30 Jul 2018 11:28:21 -0400 (EDT) Received: by mail-qk0-f199.google.com with SMTP id q3-v6so11475649qki.4 for ; Mon, 30 Jul 2018 08:28:21 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id h52-v6sor5461624qtc.76.2018.07.30.08.28.18 for (Google Transport Security); Mon, 30 Jul 2018 08:28:18 -0700 (PDT) Date: Mon, 30 Jul 2018 11:31:13 -0400 From: Johannes Weiner Subject: Re: [PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure Message-ID: <20180730153113.GB4567@cmpxchg.org> References: <6dbc33bb-f3d5-1a46-b454-13c6f5865fcd@virtuozzo.com> <20180413113855.GI17484@dhcp22.suse.cz> <8a81c801-35c8-767d-54b0-df9f1ca0abc0@virtuozzo.com> <20180413115454.GL17484@dhcp22.suse.cz> <20180413121433.GM17484@dhcp22.suse.cz> <20180413125101.GO17484@dhcp22.suse.cz> <20180726162512.6056b5d7c1d2a5fbff6ce214@linux-foundation.org> <20180727193134.GA10996@cmpxchg.org> <20180729192621.py4znecoinw5mqcp@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180729192621.py4znecoinw5mqcp@esperanza> Sender: owner-linux-mm@kvack.org List-ID: To: Vladimir Davydov Cc: Andrew Morton , Michal Hocko , Kirill Tkhai , cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org On Sun, Jul 29, 2018 at 10:26:21PM +0300, Vladimir Davydov wrote: > On Fri, Jul 27, 2018 at 03:31:34PM -0400, Johannes Weiner wrote: > > That said, the lifetime of the root reference on the ID is the online > > state, we put that in css_offline. Is there a reason we need to have > > the ID ready and the memcg in the IDR before onlining it? > > I fail to see any reason for this in the code. Me neither, thanks for double checking. The patch also survives stress testing cgroup creation and destruction with the script from 73f576c04b94 ("mm: memcontrol: fix cgroup creation failure after many small jobs"). > > Can we do something like this and not mess with the alloc/free > > sequence at all? > > I guess so, and this definitely looks better to me. Cool, then I think we should merge Kirill's patch as the fix and mine as a follow-up cleanup. ---