linux-kernel - Re: [PATCH] tools/vm/page_owner_sort.c: add switch between culling by stacktrace and txt

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>] [day] [month] [year] [list]

Date:   Wed, 23 Mar 2022 12:08:05 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Yinan Zhang <zhangyinan2019@...il.szu.edu.cn>
Cc:     Sean Anderson <seanga2@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/vm/page_owner_sort.c: add switch between culling
 by stacktrace and txt

On Wed, 23 Mar 2022 10:05:28 +0800 Yinan Zhang <zhangyinan2019@...il.szu.edu.cn> wrote:

> >> *(&list[i].txt+offset)) != 0) {
> >>               list2[count++] = list[i];
> >>           } else {
> >>               list2[count-1].num += list[i].num;
> >>
> >
> >
> You are right. Due to timestamp etc, it's almost impossible to
> 
> cull by txt. And I did observe some blocks differ in head and same in
> 
> stack trace on my linux. The examples I mentioned in patch are
> 
> part of them.
> 
> 
> Besides, --cull has been added in patch:
> 
> tools/vm/page_owner_sort.c: support for user-defined culling rules
> 

So should I drop this patch?