linux-kernel - Re: [PATCH] kho: print which scratch buffer failed to be reserved

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: <CA+CK2bAG0byyZ0CF+jHq2m8bAMq2ACxtGrtQV2XvP8i=UH04Sg@mail.gmail.com>
Date: Thu, 22 Jan 2026 14:35:15 -0500
From: Pasha Tatashin <pasha.tatashin@...een.com>
To: Pratyush Yadav <pratyush@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Alexander Graf <graf@...zon.com>, 
	Mike Rapoport <rppt@...nel.org>, kexec@...ts.infradead.org, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, Samiullah Khawaja <skhawaja@...gle.com>, 
	David Matlack <dmatlack@...gle.com>, Jason Miu <jasonmiu@...gle.com>
Subject: Re: [PATCH] kho: print which scratch buffer failed to be reserved

On Fri, Jan 16, 2026 at 11:54 AM Pratyush Yadav <pratyush@...nel.org> wrote:
>
> From: "Pratyush Yadav (Google)" <pratyush@...nel.org>
>
> When scratch area fails to reserve, KHO prints a message indicating
> that. But it doesn't say which scratch failed to allocate. This can be
> useful information for debugging. Even more so when the failure is hard
> to reproduce.
>
> Along with the current message, also print which exact scratch area
> failed to be reserved.
>
> Signed-off-by: Pratyush Yadav (Google) <pratyush@...nel.org>

Reviewed-by: Pasha Tatashin <pasha.tatashin@...een.com>