Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3602658ybc; Thu, 14 Nov 2019 11:38:46 -0800 (PST) X-Google-Smtp-Source: APXvYqz3CVEfzo6hKcO7lG8RN1NSiDS7ZvGK4BKrdG/d9IcmN9mFwBG7mLAZvsamVp6+u8OM7Bsy X-Received: by 2002:adf:9f52:: with SMTP id f18mr9697319wrg.51.1573760326653; Thu, 14 Nov 2019 11:38:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573760326; cv=none; d=google.com; s=arc-20160816; b=AuWN1K4S6wKR3ViGTeKIdycn57PkcFedyJhy3lk2iH7E6GhmlE3y1ggJG6oTdKUGSm nsI/T9NRbEMsPykhGN5N3XahXR9s3I+8Bev5VPG0ROJRJu6Oly8C6WV96JL05CoWtxMN stCdJspXWg7KcpAgNVIONcgy7vFzypHQ/zQ2v8eQ68AJKj2QYLqC+fEP0Hem7nTVjR0d jguVS03cXS3eGowWk0d0O4VkAUZk7gSOLEWgKO3bOSbPNYdGGvg4fVt3kKpRcafMthrp q3mcZngb2MzG2v2CUxzKEUd5zyzDWkFNizvtXawBN4+pXz1gJwDufbA1omvuuml1MFil bj6g== 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=tF0XSiOOM4tP9PdsxkxIErJ4+gw4ppk85TdOV+UrcBI=; b=mdLRM7H1RJA9TPAXpgo34xLHRDFX4rMO3Q3drHGiSCSS1+ZtdU2A+RoenvP8TOrOSo KLAuKBsQaEJMSrYzlPqPIqtzhdwWObQCKWFKdqskfZLOOwh9wYB5tZ4VA+ydPM5SwvLL ZNAyqKSIM1WNqxx3e2ntHPrhKGToAXA86o+A6a3Ihkr2fgOnRkqxoqH/tM5EcfPuoCP5 o9BFInkTj39rdoi0d266hMEv4fpvebhoLdc0oTFjJD/QQQWg7wtKlr6pc1edesT7BC7C jSxZwpvxNrwMBFNGyJPYChI9bCuFzR5iLhE/UGNqolt/HoA+ISqx4kF3kYm3DkTLV7RG hiHw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k24si4677519edk.367.2019.11.14.11.38.20; Thu, 14 Nov 2019 11:38:46 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726661AbfKNTdn (ORCPT + 99 others); Thu, 14 Nov 2019 14:33:43 -0500 Received: from mx2.suse.de ([195.135.220.15]:55164 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726444AbfKNTdn (ORCPT ); Thu, 14 Nov 2019 14:33:43 -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 D2A13B2AD; Thu, 14 Nov 2019 19:33:41 +0000 (UTC) Date: Thu, 14 Nov 2019 20:33:40 +0100 From: Michal Hocko To: Tejun Heo Cc: Roman Gushchin , Michal =?iso-8859-1?Q?Koutn=FD?= , "linux-mm@kvack.org" , Andrew Morton , Johannes Weiner , "linux-kernel@vger.kernel.org" , Kernel Team , "stable@vger.kernel.org" Subject: Re: [PATCH 1/2] mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm() Message-ID: <20191114193340.GA24848@dhcp22.suse.cz> References: <20191106225131.3543616-1-guro@fb.com> <20191113162934.GF19372@blackbody.suse.cz> <20191113170823.GA12464@castle.DHCP.thefacebook.com> <20191114191657.GN20866@dhcp22.suse.cz> <20191114192018.GJ4163745@devbig004.ftw2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191114192018.GJ4163745@devbig004.ftw2.facebook.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 On Thu 14-11-19 11:20:18, Tejun Heo wrote: > Hello, > > On Thu, Nov 14, 2019 at 08:16:57PM +0100, Michal Hocko wrote: > > Then what is the point of this function and what about all other users? > > It is useful for controlling admissions of new userspace visible uses > - e.g. a tracepoint shouldn't be allowed to be attached to a cgroup > which has already been deleted. I am not sure I understand. Roman says that the cgroup can get offline right after the function returns. How is "already deleted" different from "just deleted"? I thought that the state is preserved at least while the rcu lock is held but my memory is dim here. > We're just using it too liberally. Can we get a doc update to be explicit about sensible usecases so that others can be dropped accordingly? -- Michal Hocko SUSE Labs