From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 64C8CC54FCF for ; Tue, 24 Mar 2020 01:08:39 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 2205120722 for ; Tue, 24 Mar 2020 01:08:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="NwnIBNso" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2205120722 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id BEBF76B00A4; Mon, 23 Mar 2020 21:08:38 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B76246B00A5; Mon, 23 Mar 2020 21:08:38 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A8BB96B00A6; Mon, 23 Mar 2020 21:08:38 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0224.hostedemail.com [216.40.44.224]) by kanga.kvack.org (Postfix) with ESMTP id 8ADFB6B00A4 for ; Mon, 23 Mar 2020 21:08:38 -0400 (EDT) Received: from smtpin09.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 6D0308249980 for ; Tue, 24 Mar 2020 01:08:38 +0000 (UTC) X-FDA: 76628470716.09.swing49_112f60435d91e X-HE-Tag: swing49_112f60435d91e X-Filterd-Recvd-Size: 2433 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf42.hostedemail.com (Postfix) with ESMTP for ; Tue, 24 Mar 2020 01:08:37 +0000 (UTC) Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D072220714; Tue, 24 Mar 2020 01:08:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585012117; bh=N8ny1ddSH/WDtO8Ur8IBPuVWrQVYsU/hhfFIi/kKH78=; h=Date:From:To:Subject:In-Reply-To:References:From; b=NwnIBNso0VcDySPOFtACQf/IyXu0Mx81CcufV3Yhj8Jn7rhCANQZJz6uoNGQyDOZy 5k1pBQ/MUwcPz2GnuBF6J1L2ryc47EjmuCy9nKNzp5AbYhbUmSQc9lLA6uAKVuDYal UXd78+ngt+C8WcQe+0oJMHCjjpl/4SZZ2BwT4tWk= Date: Mon, 23 Mar 2020 18:08:36 -0700 From: Andrew Morton To: Roman Gushchin , Johannes Weiner , Michal Hocko , , , , Bharata B Rao , Subject: Re: [PATCH] mm: fork: fix kernel_stack memcg stats for various stack implementations Message-Id: <20200323180836.2d824f5d45f2f5dce729d5b2@linux-foundation.org> In-Reply-To: <20200323180633.5e75654282d076d74766bd88@linux-foundation.org> References: <20200303233550.251375-1-guro@fb.com> <20200321164856.be68344b7fac84b759e23727@linux-foundation.org> <20200324004221.GA36662@carbon.dhcp.thefacebook.com> <20200323180358.7603217aa9955f298255da4e@linux-foundation.org> <20200323180633.5e75654282d076d74766bd88@linux-foundation.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, 23 Mar 2020 18:06:33 -0700 Andrew Morton wrote: > And here's the altered "mm: memcg/slab: introduce > mem_cgroup_from_obj()", which I have renamed to "mm: memcg/slab: use > mem_cgroup_from_obj()": > > The end result is slightly different - mem_cgroup_from_obj() will now > end up inside #ifdef CONFIG_MEMCG_KMEM. Should I undo that? err, no, we've just fed forward the build fixes in mm-memcg-slab-introduce-mem_cgroup_from_obj-v2.patch so I think we're all good.