linux-kernel - Re: [PATCH RESEND] crash_core: export vmemmap when CONFIG_SPARSEMEM

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 for Android: free password hash cracker in your pocket

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

Date: Mon, 26 Feb 2024 11:10:37 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Huang Shijie <shijie@...amperecomputing.com>
Cc: bhe@...hat.com, patches@...erecomputing.com, vgoyal@...hat.com,
 dyoung@...hat.com, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
 k-hagio-ab@....com, lijiang@...hat.com
Subject: Re: [PATCH RESEND] crash_core: export vmemmap when
 CONFIG_SPARSEMEM_VMEMMAP is enabled

On Mon, 26 Feb 2024 10:04:33 +0800 Huang Shijie <shijie@...amperecomputing.com> wrote:

> In memory_model.h, if CONFIG_SPARSEMEM_VMEMMAP is configed,
> kernel will use vmemmap to do the __pfn_to_page/page_to_pfn,
> and kernel will not use the "classic sparse" to do the
> __pfn_to_page/page_to_pfn.
> 
> So export the vmemmap when CONFIG_SPARSEMEM_VMEMMAP is configed.
> This makes the user applications (crash, etc) get faster
> pfn_to_page/page_to_pfn operations too.

This is significantly out of sync with development trees.  Please take
a look at linux-next and redo the patch if still needed?