Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp108267rwl; Thu, 30 Mar 2023 12:56:36 -0700 (PDT) X-Google-Smtp-Source: AKy350Z3pz0hQQdPnEdlsiQ4z+PmVslxg46dFpzCzWKTHhwbqzO796O8njtLVppUPLYyZf92uzNg X-Received: by 2002:a17:906:519d:b0:939:5398:768e with SMTP id y29-20020a170906519d00b009395398768emr22041284ejk.7.1680206196516; Thu, 30 Mar 2023 12:56:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680206196; cv=none; d=google.com; s=arc-20160816; b=wqNMI0eEDoNOHYmDXDr5eQiUsTwAypKxzs/sf2wFWv6opxUTUtiyDW5H+ufcq3IMND ETWf3qCdIDBuosLz65btMauudOenF+cC4dsSVyyxJy1GzlZ1Qk0hIsRI96qyannSyETC eLkejLpFzcw1GIutSTRZ9p8zhA27wUwdHzV81cflE8PC2NEV3npQq5+r8PrC2Bh2pn78 LEt8yRdmJRmbclXPwTVHUn0Mp8xqm95YE4HI4sRewD2Inx6jicTYA7aBcmtXBx6ZhF94 7KlW4vZLWKy/H4PLBhpJ/S4+bN/cw5Mx1oulPhbAnOvASyoTG0rH9ok9VJg/vDl4s4Yu 2Kjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=KCcB5OY8SQyKSb7z+4YaRuPUYL+j2up2EUbXt0Mw2dI=; b=h4vH8dJVea+QgF21OkvBjaQ+wkuvkAQMAd/6JmthfTAbuBmIeG9lauRmPkF6zP7v5T HgwJhakgMPD2Wr2bp4wstjhIkyHQzu6JgU5UjfwtebUrzYN3DdYJg5Mz0k5IRPQXwBtv TZOiyZokY9NPRCXubSARm4xfLjCajpzX0gXyRqKMaTl4/ryDGOsGqZYN3yvGsN0+RdOp mb3DXsQPYSJgOUu+l/hB38resuNT2FYVgrs6j4xTzXHfD1jMVgJRJgwx7+BTwo+6k2bk YRmDLs4GFzdFf86Gs3RYdaro8nspbQm7Kw8RN29fqLe6hVWWLWNfHXYkiSuNsSxH0mHt tWqA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=s0h7rvKG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p15-20020a170906a00f00b00933260c6385si395070ejy.230.2023.03.30.12.56.11; Thu, 30 Mar 2023 12:56:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=s0h7rvKG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231814AbjC3Tzh (ORCPT + 99 others); Thu, 30 Mar 2023 15:55:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57534 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231650AbjC3Tzf (ORCPT ); Thu, 30 Mar 2023 15:55:35 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 927861024E for ; Thu, 30 Mar 2023 12:55:34 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id r187so24985460ybr.6 for ; Thu, 30 Mar 2023 12:55:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1680206133; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=KCcB5OY8SQyKSb7z+4YaRuPUYL+j2up2EUbXt0Mw2dI=; b=s0h7rvKGInOi0krE3W8LR7VJ4S4A7z47vZbouVSzXWKE9OjUtQB8Kt/A8uBBIsuYGg 4OuHcmQ4+Q4F1sDHKG50ARafeyCKVXEeGq498f2n0uv3uMtsJe7LztATHDsOfRm0/Uv3 qBEgbeb3R3H6vPV2spHKFSswGjl0VxrnrilRHlDX4iyrlduGRh+HZ052Ab6z9K8z8vmK rSDI8ZX7m+n9V4wmKZOrZoNCzwkLWJ8PTOJBCUonW3k5MJRT6IJxOmwtin//hOXolTMo VG23NIaNap7GNfw+Ghsn50qUCERUmmyivY8RTvZvz2qsDe5q2fUUPL2UXjXx/KTDJFpL /2nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680206133; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KCcB5OY8SQyKSb7z+4YaRuPUYL+j2up2EUbXt0Mw2dI=; b=X7n8Aep6WDt+HX/OXwvwTpYQrz3cE+NDV2LyO0AoP4zOrYm6J/esGse5I9aMSjaKmK cdFrxm8ZXMb5SpMHxnVT7Y/biCynqLzJrMS/s0o/WDvQcKOVcefvJ6vTVQAkklO1j1pZ /FU9k8CaHtnH1gS/2dCKUaMtS6J3ucXJ5O6sc+ACsNMdXv7lxqiyc5O3y3eRb55DZei9 XbeupXYAZZy5OFEKx0BtNlVEG0id8NLrQcnTtdb303KsLbErmpnpMWGfZkn72Wa9eK5/ lrDAfkMo1/I3Nefv+wsdGUfEi9QmTvJqxvLT9Jp6u9jT551uE5P1N4zmSBuLinCQQPCd 2vCQ== X-Gm-Message-State: AAQBX9dnzUvMdKla3Pz/EpWMtLPjPEIMvrOgz7iErQK1DLmkocsr4+10 zX7sFBHqBmerPmWIs4R23IpV4yEtzbeJPRuxIoqmig== X-Received: by 2002:a05:6902:154e:b0:b77:d2db:5f8f with SMTP id r14-20020a056902154e00b00b77d2db5f8fmr15921642ybu.12.1680206133587; Thu, 30 Mar 2023 12:55:33 -0700 (PDT) MIME-Version: 1.0 References: <20230330133822.66271-1-mathieu.desnoyers@efficios.com> <20230330124230.9f3d4f63374eb15a3b990ff8@linux-foundation.org> In-Reply-To: <20230330124230.9f3d4f63374eb15a3b990ff8@linux-foundation.org> From: Shakeel Butt Date: Thu, 30 Mar 2023 12:55:22 -0700 Message-ID: Subject: Re: [PATCH 1/1] mm: Fix memory leak on mm_init error handling To: Andrew Morton Cc: Mathieu Desnoyers , linux-kernel@vger.kernel.org, Marek Szyprowski , linux-mm@kvack.org, stable@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-15.7 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,ENV_AND_HDR_SPF_MATCH, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 30, 2023 at 12:42=E2=80=AFPM Andrew Morton wrote: > > On Thu, 30 Mar 2023 09:38:22 -0400 Mathieu Desnoyers wrote: > > > commit f1a7941243c1 ("mm: convert mm's rss stats into percpu_counter") > > introduces a memory leak by missing a call to destroy_context() when a > > percpu_counter fails to allocate. > > > > Before introducing the per-cpu counter allocations, init_new_context() > > was the last call that could fail in mm_init(), and thus there was no > > need to ever invoke destroy_context() in the error paths. Adding the > > following percpu counter allocations adds error paths after > > init_new_context(), which means its associated destroy_context() needs > > to be called when percpu counters fail to allocate. > > > > ... > > > > --- a/kernel/fork.c > > +++ b/kernel/fork.c > > @@ -1171,6 +1171,7 @@ static struct mm_struct *mm_init(struct mm_struct= *mm, struct task_struct *p, > > fail_pcpu: > > while (i > 0) > > percpu_counter_destroy(&mm->rss_stat[--i]); > > + destroy_context(mm); > > fail_nocontext: > > mm_free_pgd(mm); > > fail_nopgd: > > Is there really a leak? I wasn't able to find a version of > init_new_context() which performs allocation. > There are more than 20 archs defining this function and I couldn't check each one of them. I think we can assume there might be new allocation in the future.