linux-kernel - Re: [PATCH v3 1/2] kho: add support for preserving vmalloc allocations

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

Message-ID: <mafs0v7lih6se.fsf@kernel.org>
Date: Tue, 16 Sep 2025 15:21:37 +0200
From: Pratyush Yadav <pratyush@...nel.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Mike Rapoport <rppt@...nel.org>,  Pratyush Yadav <me@...avpratyush.com>,
  Pratyush Yadav <pratyush@...nel.org>,  Andrew Morton
 <akpm@...ux-foundation.org>,  Alexander Graf <graf@...zon.com>,  Baoquan
 He <bhe@...hat.com>,  Changyuan Lyu <changyuanl@...gle.com>,  Chris Li
 <chrisl@...nel.org>,  Pasha Tatashin <pasha.tatashin@...een.com>,
  kexec@...ts.infradead.org,  linux-mm@...ck.org,
  linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] kho: add support for preserving vmalloc allocations

On Tue, Sep 16 2025, Jason Gunthorpe wrote:

> On Mon, Sep 15, 2025 at 07:36:25PM +0300, Mike Rapoport wrote:
>> > Under the covers it all uses the generic folio based code we already
>> > have, but we should have appropriate wrappers around that code that
>> > make clear these patterns.
>> 
>> Right, but that does not mean that vmalloc preserve/restore should use the
>> public KHO APIs and avoid using internal methods.
>
> I think it does, the same way vmalloc is layered on top of the buddy
> allocator. Why wouldn't you build things in clean understandable
> layers like this?

+1

-- 
Regards,
Pratyush Yadav