linux-kernel - Re: [PATCH V2] crypto: Mark intermediary memory as clean

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]

Message-ID: <tencent_F8BAB8BB23338A9E2C1B4F4BD11BD9252E08@qq.com>
Date: Mon, 18 Aug 2025 20:43:36 +0800
From: Edward Adam Davis <eadavis@...com>
To: smueller@...onox.de
Cc: herbert@...dor.apana.org.au,
	davem@...emloft.net,
	eadavis@...com,
	linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	syzbot+e8bcd7ee3db6cb5cb875@...kaller.appspotmail.com,
	syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH V2] crypto: Mark intermediary memory as clean

On Mon, 18 Aug 2025 20:30:29 +0800, Herbert Xu wrote:
> Their values are equal, so why use sizeof to calculate?
> Similarly, "if (sizeof(intermediary) != crypto_shash_digestsize(desc->tfm)) {",
> why not just use SHA3_256_DIGEST_SIZE?
Hi Stephan Mueller, can you explain it?

BR,
Edward