Callers may query the hash digest length before getting to the code path that performs hashing, which is where the lack of support for SM3 in the backend will be reported.
Reporting a hash length of 0 is liable to cause divide by zero errors in callers. Fixes: https://gitlab.com/qemu-project/qemu/-/work_items/4786 Signed-off-by: Daniel P. Berrangé <[email protected]> --- crypto/hash.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/crypto/hash.c b/crypto/hash.c index 6ffb88bf541..42a0a8ec56f 100644 --- a/crypto/hash.c +++ b/crypto/hash.c @@ -33,9 +33,7 @@ static size_t qcrypto_hash_alg_size[QCRYPTO_HASH_ALGO__MAX] = { [QCRYPTO_HASH_ALGO_SHA384] = QCRYPTO_HASH_DIGEST_LEN_SHA384, [QCRYPTO_HASH_ALGO_SHA512] = QCRYPTO_HASH_DIGEST_LEN_SHA512, [QCRYPTO_HASH_ALGO_RIPEMD160] = QCRYPTO_HASH_DIGEST_LEN_RIPEMD160, -#ifdef CONFIG_CRYPTO_SM3 - [QCRYPTO_HASH_ALGO_SM3] = QCRYPTO_HASH_DIGEST_LEN_SM3, -#endif + [QCRYPTO_HASH_ALGO_SM3] = QCRYPTO_HASH_DIGEST_LEN_SM3, }; size_t qcrypto_hash_digest_len(QCryptoHashAlgo alg) -- 2.56.0
