linux-kernel - Re: [PATCH] mm/page_owner.c: allow page_owner with given start

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

Date:   Tue, 26 Jul 2022 16:03:47 +0200
From:   "Vlastimil Babka (SUSE)" <vbabka@...nel.org>
To:     Kassey Li <quic_yingangl@...cinc.com>,
        Matthew Wilcox <willy@...radead.org>
Cc:     akpm@...ux-foundation.org, minchan@...nel.org,
        iamjoonsoo.kim@....com, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, quic_guptap@...cinc.com
Subject: Re: [PATCH] mm/page_owner.c: allow page_owner with given
 start_pfn/count

On 7/25/22 10:39, Kassey Li wrote:
> hi, Matthew:
>     sorry for the delay, I just started to learn how to upstream patch, and
> setup my Thunderbird with plain text only.
>     you are right, two users will cause problem here.
>     the uses case is dump CMA area to understand the page usage in a given
> cma pool. 2nd, dump whole memory page owner is very time cost, mostly our
> android device has 8G memory now.
>     I will research and check again, if you have more idea on this , please
> kindly to share.

You could try employing lseek() to specify the start pfn, and as for end
pfn, the process can just stop reading and close when it has seen enough?

> BR
> Kassey
> 
> On 7/22/2022 11:38 PM, Matthew Wilcox wrote:
>> On Fri, Jul 22, 2022 at 11:08:10PM +0800, Kassey Li wrote:
>>> by default, page_owner iterates all page from min_low_pfn to
>>> max_pfn, this cost too much time if we want an alternative pfn range.
>>>
>>> with this patch it allows user to set pfn range to dump the page_onwer.
>>
>> This is a really bad UI.  If two users try to do different ranges at the
>> same time, it'll go wrong.  What use cases are you actually trying to
>> solve?
>