linux-kernel - Re: [PATCH] crypto: padlock-sha

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: <aUI4CGp6kK7mxgEr@gondor.apana.org.au>
Date: Wed, 17 Dec 2025 12:56:40 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: AlanSong-oc <AlanSong-oc@...oxin.com>
Cc: Eric Biggers <ebiggers@...nel.org>, linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org, larryw3i <larryw3i@...h.net>,
	stable@...r.kernel.org, CobeChen@...oxin.com, GeorgeXue@...oxin.com,
	HansHu@...oxin.com, LeoLiu-oc@...oxin.com, TonyWWang-oc@...oxin.com,
	YunShen@...oxin.com
Subject: Re: [PATCH] crypto: padlock-sha - Disable broken driver

On Wed, Dec 17, 2025 at 12:30:57PM +0800, AlanSong-oc wrote:
>
> Given the lack of a verification platform for the current padlock-sha
> driver, and the fact that these CPUs are rarely used today, extending
> the existing padlock-sha driver to support the ZHAOXIN platform is very
> difficult. To address the issues encountered when using the padlock-sha
> driver on the ZHAOXIN platform, would it be acceptable to submit a
> completely new driver that aligns with the previous advice?

Perhaps it would be easier if you just added Zhaoxin support to
lib/crypto instead?

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt