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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <aWzPXXqc_jWjh4rD@kernel.org>
Date: Sun, 18 Jan 2026 14:17:33 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Pratyush Yadav <pratyush@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Graf <graf@...zon.com>,
	Pasha Tatashin <pasha.tatashin@...een.com>,
	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 04:54:11PM +0000, Pratyush Yadav 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: Mike Rapoport (Microsoft) <rppt@...nel.org>

-- 
Sincerely yours,
Mike.