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;
MIME-Version: 1.0
References: <20230704101942.2819426-1-liushixin2@huawei.com>
In-Reply-To: <20230704101942.2819426-1-liushixin2@huawei.com>
From:   Muchun Song <songmuchun@bytedance.com>
Date:   Tue, 4 Jul 2023 19:49:18 +0800
Message-ID: <CAMZfGtWW_LhaZe4uUNMiLVs0n48vdA+xdbG14UPz6u0Y3RbvNQ@mail.gmail.com>
Subject: Re: [External] [PATCH] bootmem: remove the vmemmap pages from
 kmemleak in free_bootmem_page
To:     Liu Shixin <liushixin2@huawei.com>
Cc:     Matthew Wilcox <willy@infradead.org>,
        Mike Kravetz <mike.kravetz@oracle.com>,
        Oscar Salvador <osalvador@suse.de>,
        Andrew Morton <akpm@linux-foundation.org>,
        linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        muchun.song@linux.dev
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Jul 4, 2023 at 5:23=E2=80=AFPM Liu Shixin <liushixin2@huawei.com> w=
rote:
>
> commit dd0ff4d12dd2 ("bootmem: remove the vmemmap pages from kmemleak in
> put_page_bootmem") fix an overlaps existing problem of kmemleak. But the
> problem still existed when HAVE_BOOTMEM_INFO_NODE is disabled, because in
> this case, free_bootmem_page() will call free_reserved_page() directly.
>
> Fix the problem by adding kmemleak_free_part() in free_bootmem_page()
> when HAVE_BOOTMEM_INFO_NODE is disabled.
>
> Fixes: f41f2ed43ca5 ("mm: hugetlb: free the vmemmap pages associated with=
 each HugeTLB page")
> Signed-off-by: Liu Shixin <liushixin2@huawei.com>

Acked-by: Muchun Song <songmuchun@bytedance.com>

Thanks.