Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp900031pxb; Tue, 1 Feb 2022 12:45:48 -0800 (PST) X-Google-Smtp-Source: ABdhPJwj+RDeKf2NwR3VrbSjooAHvdj720AI2gX6a34XbZXPZ1sObqtFkRKWhvpVN98sNnohi3m6 X-Received: by 2002:a17:90b:181:: with SMTP id t1mr4334856pjs.240.1643748348233; Tue, 01 Feb 2022 12:45:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643748348; cv=none; d=google.com; s=arc-20160816; b=1HS6FYbndgcbEIJrsPljQHgWPm1nIcIZe9odMuxzK2Jv3tbK9IVBJtOzKoAAXJrLMj FmrYWpXRRTzzB8n1FuKXUdsfYIQoOLOsaeFlAnkz8mcPmnK74/xKDl7ZfbhwoFA1szUY Zgptyz1lxfMF7CLiTulwoeb7rjG2M3He1bIXhXZMRs/McURJhY7XcgahDWi9Qfvzmz3I Z6SCnZNNZOMTNnX/hMhbPyoh7kv2KyxNOW0r4SjVntztVyA7PWMabXCmnrskBgefP+wV 1lCX2mN3TMy0vaSYXKHFfKgmj38ACfK6uPso737lHsyhDkx+f0kqVpkYOn521/1YHHPH KwNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=PaMPeaT7bqTywU/6EXOdBYInz5ZUKSgh51n5zqNu8us=; b=ZFJ3ceepKFeNupZC/WQ7tXspoN2m59DD9xqLc53p+pib/90hijjwz57WeiWD1QEQzF tX/U/sVUFREqqXMhfC4eEFNkD6yawRMglpmThQUmu6CMYmlXzrGi/6oRXmtDM5iZl9st ofS4QfOy7ov+x6NHZIX511j1uENwouZrz18w0fD820Xer7igGrJuDNsgN36M7yRWCnIR aLxf0NsH+wQjD2JlG/ktZpz7o3E6h2SAZTFfZ2Zg9VAtRwcXSV0mQn7YygAglX7xw/fx T020lSOSwwmpVdvTkN8VrtZmvoC061B1OCksN0vxMwS5HQ959B4QZ7oU1xI038KTjum+ tcXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aHAxZStW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id oc18si3630723pjb.188.2022.02.01.12.45.36; Tue, 01 Feb 2022 12:45:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aHAxZStW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1381010AbiAaRZk (ORCPT + 99 others); Mon, 31 Jan 2022 12:25:40 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:53583 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380922AbiAaRZM (ORCPT ); Mon, 31 Jan 2022 12:25:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643649911; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PaMPeaT7bqTywU/6EXOdBYInz5ZUKSgh51n5zqNu8us=; b=aHAxZStWqkUrjPvqX9Txg0mP8o1eBsmhBW2JRC1t4oslin+hOdgyTWy1D8FleXk6Dbd266 4kVIx3hSwNWx5PYGbIoOzdEYImRiuZeOsnoATbb3+pHKuUM93OgquhCwwRHesLn1Q9s6ou aUwp4c5amAuDRFrehZLoODKvrdDoODY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-558-WevAcsvfPmSx_CbH-QId1w-1; Mon, 31 Jan 2022 12:25:09 -0500 X-MC-Unique: WevAcsvfPmSx_CbH-QId1w-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3450793921; Mon, 31 Jan 2022 17:25:07 +0000 (UTC) Received: from [10.22.16.244] (unknown [10.22.16.244]) by smtp.corp.redhat.com (Postfix) with ESMTP id BD20F6E202; Mon, 31 Jan 2022 17:25:05 +0000 (UTC) Message-ID: <9abc9cb8-8734-90b0-c495-8df89c7bb579@redhat.com> Date: Mon, 31 Jan 2022 12:25:05 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH 1/3] mm, memcg: Don't put offlined memcg into local stock Content-Language: en-US To: Roman Gushchin Cc: Johannes Weiner , Michal Hocko , Vladimir Davydov , Andrew Morton , Vlastimil Babka , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, Shakeel Butt , Muchun Song References: <20211001190938.14050-1-longman@redhat.com> <20211001190938.14050-2-longman@redhat.com> <95ba1931-e9c9-45c3-b080-d28f2ad368a7@redhat.com> From: Waiman Long In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/31/22 12:19, Roman Gushchin wrote: > On Mon, Jan 31, 2022 at 12:15:19PM -0500, Waiman Long wrote: >> On 1/31/22 12:09, Waiman Long wrote: >>> On 1/31/22 12:01, Roman Gushchin wrote: >>>> On Sun, Jan 30, 2022 at 10:55:56PM -0500, Waiman Long wrote: >>>>> On 10/1/21 19:51, Roman Gushchin wrote: >>>>>> On Fri, Oct 01, 2021 at 03:09:36PM -0400, Waiman Long wrote: >>>>>>> When freeing a page associated with an offlined memcg, refill_stock() >>>>>>> will put it into local stock delaying its demise until another memcg >>>>>>> comes in to take its place in the stock. To avoid that, we now check >>>>>>> for offlined memcg and go directly in this case to the slowpath for >>>>>>> the uncharge via the repurposed cancel_charge() function. >>>>>> Hi Waiman! >>>>>> >>>>>> I'm afraid it can make a cleanup of a dying cgroup slower: for every >>>>>> released page we'll potentially traverse the whole cgroup tree and >>>>>> decrease atomic page counters. >>>>>> >>>>>> I'm not sure I understand the benefits we get from this change which >>>>>> do justify the slowdown on the cleanup path. >>>>>> >>>>>> Thanks! >>>>> I was notified of a lockdep splat that this patch may help to prevent. >>>> Would you mind to test this patch: >>>> https://www.spinics.net/lists/cgroups/msg31244.html ? >>>> >>>> It should address this dependency. >>> Thanks for the pointer. I believe that your patch should be able to >>> address this circular locking dependency. >>> >>> Feel free to add my >>> >>> Reviewed-by: Waiman Long >> BTW, have you posted it to lkml? If not, would you mind doing so? > Not yet. > > I was waiting for Alexander to confirm that it resolves the originally reported > issue. I just pinged him, will wait for tomorrow and post the patch in any case. > > Thanks! I see. This is not a problem that is easily reproducible. You need to hit the right timing for the lockdep splat to appear. Regards, Longman