Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp425007ybc; Fri, 22 Nov 2019 07:24:08 -0800 (PST) X-Google-Smtp-Source: APXvYqyw5kto/YbryuiLnKY2Hu+g/zuzBX+GFwbJxPulaj+ZAckGD2QPxOhq0xKBUUR6HHXCiW0x X-Received: by 2002:a17:906:891:: with SMTP id n17mr20819071eje.230.1574436248206; Fri, 22 Nov 2019 07:24:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574436248; cv=none; d=google.com; s=arc-20160816; b=alLI5G/BXowVByaU2JC0XQT/Wv6ebSFrr5ffRup7kKLAKSdUJLy1+0FoSTYEOMr8UC M88T+/jvNXV0zy8ukhsx7rGeB96IYJRs0TYEQ749XlZbmOV6KRnI5riHUScrcgptcyVs CXpbvc/E9AkGzXsnvWW41Kp5vQbvCAAbCWdLCh6KM9HDP/TaVfiq2N7lATO/MA8wkce+ n76MItpGg+WmnQVfyFcNvp05F8i2Li44HLBo7jpSe2aAJZqZQk3Op1PqaGHvkd8xyScK i372l66EjgtPAgSdKnULnN8fs3XM0O7IxfAGX2WKm3udylYK6BcL2empYF8Ynt0QxFw+ CVSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=CLBkjzZugkp6natIzqE108W6M6bli4p2/Ky+zdJB5+A=; b=ANjHeImb3RpwRN7LY2mkhuo7KIc71gSaYqIqw92ir503xbbI9OcNsTBmdk1bvzrUlA vS770o4ECCqQ24I0NDptwn1gxSr0QOmTaH/BhpSzuuUSOo+/LV3Iv9VD1qLCB5TtzEeI Iee9cfv3IYiQ3kWUAL3sHBRPaxgLDBDEoleTCXP3+q0WuS9YcAoYTOd7E8O1Jz26pXh4 9Nwgpi+xvqJTCISQSONRI98/hcNgvYFCmgJZ29uiv0/1dy4MUEZbrQSRAK/jSN9X1bqT xyfNDVHLa8KrdhdouBGGEoB3EWxG7ROqQQIz4abmBEQWgGkQQAFJDTTLl7qX2OvIUCdJ JiWA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ci3si4474980ejb.37.2019.11.22.07.23.43; Fri, 22 Nov 2019 07:24:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726846AbfKVPTw (ORCPT + 99 others); Fri, 22 Nov 2019 10:19:52 -0500 Received: from mx2.suse.de ([195.135.220.15]:42770 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726045AbfKVPTw (ORCPT ); Fri, 22 Nov 2019 10:19:52 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 78D21AD12; Fri, 22 Nov 2019 15:19:50 +0000 (UTC) Date: Fri, 22 Nov 2019 16:19:48 +0100 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: "Li,Rongqing" Cc: "linux-kernel@vger.kernel.org" , "tj@kernel.org" , "lizefan@huawei.com" , "hannes@cmpxchg.org" , "cgroups@vger.kernel.org" Subject: Re: mount cgroup with "already mounted or cgroup busy" Message-ID: <20191122151948.GB14375@blackbody.suse.cz> References: <11be9352e1e54ebebad078b1dac7b670@baidu.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yEPQxsgoJgBvi8ip" Content-Disposition: inline In-Reply-To: <11be9352e1e54ebebad078b1dac7b670@baidu.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Li. On Wed, Oct 30, 2019 at 09:32:41AM +0000, "Li,Rongqing" wrote: > I meet a issue, and not sure if it is normal It is a consequence of how cgroup state is retained. I considered a "trivial" fix, however, I learnt later it'd be a revert (and hence regression) of=20 3c606d35fe97 "cgroup: prevent mount hang due to memory controller lifetime" > Using the below script, the last line mount will fail after unmount > And it will fail until reboot system The cause is that controllers remained pinned to the same root. You can unpin them by mounting/unmounting again attached to the same root (i.e. cpu,cpuset again). (Perhaps the logic in cgroup1_root_to_use may be changed to cope better with the "stateless" controllers.) Michal --yEPQxsgoJgBvi8ip Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEEoQaUCWq8F2Id1tNia1+riC5qSgFAl3X/JAACgkQia1+riC5 qSjBrw//bqjJVzaKkfcqi3QnWN7tcJnRB4kscGgj394bxZWDEaDCt5hnUblyD85Z MNTSmkcTGGhGjRmnjKDYPDXr18PaOvVZu5etkpGYCza7SZ/g/MH/9W3DstVwVOzA UudRbYwOHwieb93kKPNeE+uVKiKmXT+5AEpDCgqiQKPKRtdwRkJnxBPe0+Ii/cj3 YCo4ydhMQoDv5k7Vze1ZCLS3zAKNDJQQmcp3lPaBCDdlkTe0VE6DGFJwhQmZE3S0 4ezWkuDKpY+ab429voibjKskWfmfZI7miX6iMcx7txe1o8EYzMoKmCexWusNCSSa x7Eoi5pLmj+FK0DbMU+3H3mH2h/W0YmeK/d5ZbYI33R8DTRt2vPQgH3WiSVVqtay IITNljYshLP0VPWPUM+lWtO0QZzAhUGDAWpIXVclr1OymQxa9k/fRDrho+138QNM 8RChlt82rkXeF9v8OfgdZx8vvJVfCfxzKf61R2RK1qas8LB+F87m2hSjUfwAUX0K BW5LTyyPwu7Fgj8bq8W1wNPk425QwZHYk83uPJnFXLiimUR5jK5Ixs1iT++l7Aci E7dZsX3bVcaCx2YCFA1TYjF3eTqu4fKooChHQT3RNTHXcIbQHmvaZLpGhWVNk8EW gZ39bdXJYxxLBpSIDmoiDOWkjMREW1dRZjMrN3pkHWPEcl0AsOw= =WHd6 -----END PGP SIGNATURE----- --yEPQxsgoJgBvi8ip--