linux-kernel - Re: [PATCH 1/2] mm/page_owner.c: introduce vmalloc allocator for page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YjlCTOrCUHnVxIqj@casper.infradead.org>
Date:   Tue, 22 Mar 2022 03:28:12 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Yinan Zhang <zhangyinan2019@...il.szu.edu.cn>
Cc:     akpm@...ux-foundation.org, vbabka@...e.cz,
        william.kucharski@...cle.com, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, yejiajian2018@...il.szu.edu.cn,
        hanshenghong2019@...il.szu.edu.cn, caoyixuan2019@...il.szu.edu.cn,
        zhaochongxi2019@...il.szu.edu.cn, yuhongf@....edu.cn
Subject: Re: [PATCH 1/2] mm/page_owner.c: introduce vmalloc allocator for
 page_owner

On Tue, Mar 22, 2022 at 11:22:24AM +0800, Yinan Zhang wrote:
> An application's memory consumption is high and keeps increasing,
> then it is suspected of having memory leak. There are several
> commonly used memory allocators: slab, cma, vmalloc, etc. The memory
> leak identification can be speed up if page information allocated
> by an individual allocator are analyzed individually. This patch
> introduce vmalloc allocator for page_owner.

Why is /proc/vmallocinfo not enough?