From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alejandro Zeise <alejandro.zeise@seagate.com>
Cc: qemu-arm@nongnu.org, kris.conklin@seagate.com,
jonathan.henze@seagate.com, evan.burgess@seagate.com,
clg@kaod.org, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 08/15] tests/unit/test-crypto-hash: accumulative hashing
Date: Thu, 8 Aug 2024 18:18:39 +0100 [thread overview]
Message-ID: <ZrT972O-HcxMkT9L@redhat.com> (raw)
In-Reply-To: <20240807195122.2827364-9-alejandro.zeise@seagate.com>
On Wed, Aug 07, 2024 at 07:51:15PM +0000, Alejandro Zeise wrote:
> Added an accumulative hashing test. Checks for functionality of
> the new hash create, update, finalize and free functions.
>
> Signed-off-by: Alejandro Zeise <alejandro.zeise@seagate.com>
> ---
> tests/unit/test-crypto-hash.c | 48 +++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/tests/unit/test-crypto-hash.c b/tests/unit/test-crypto-hash.c
> index 1f4abb822b..2bf9bcb6a0 100644
> --- a/tests/unit/test-crypto-hash.c
> +++ b/tests/unit/test-crypto-hash.c
> @@ -1,6 +1,7 @@
> /*
> * QEMU Crypto hash algorithms
> *
> + * Copyright (c) 2024 Seagate Technology LLC and/or its Affiliates
> * Copyright (c) 2015 Red Hat, Inc.
> *
> * This library is free software; you can redistribute it and/or
> @@ -241,6 +242,52 @@ static void test_hash_base64(void)
> }
> }
>
> +static void test_hash_accumulate(void)
> +{
> + QCryptoHash *hash;
Move this inside the for() and use 'g_autoptr(QCryptoHash) hash = NULL'
> + size_t i;
> +
> + for (i = 0; i < G_N_ELEMENTS(expected_outputs) ; i++) {
> + struct iovec iov[3] = {
Don't need to declare it '[3]' just '[]' as, then....
> + { .iov_base = (char *)INPUT_TEXT1, .iov_len = strlen(INPUT_TEXT1) },
> + { .iov_base = (char *)INPUT_TEXT2, .iov_len = strlen(INPUT_TEXT2) },
> + { .iov_base = (char *)INPUT_TEXT3, .iov_len = strlen(INPUT_TEXT3) },
> + };
> + uint8_t *result = NULL;
g_autofree uint8_t *result = NULL;
> + size_t resultlen = 0;
> + int ret;
> + size_t j;
> +
> + if (!qcrypto_hash_supports(i)) {
> + continue;
> + }
> +
> + hash = qcrypto_hash_new(i, &error_fatal);
> + g_assert(hash != NULL);
> +
> + /* Add each iovec to the hash context separately */
> + for (j = 0; j < 3; j++) {
...instead of 'j < 3' use 'j < G_N_ELEMENTS(iov)'
> + ret = qcrypto_hash_updatev(hash,
> + &iov[j], 1,
> + &error_fatal);
> +
> + g_assert(ret == 0);
> + }
> +
> + ret = qcrypto_hash_finalize_bytes(hash, &result, &resultlen,
> + &error_fatal);
> +
> + g_assert(ret == 0);
> + g_assert(resultlen == expected_lens[i]);
> + for (j = 0; j < resultlen; j++) {
> + g_assert(expected_outputs[i][j * 2] == hex[(result[j] >> 4) & 0xf]);
> + g_assert(expected_outputs[i][j * 2 + 1] == hex[result[j] & 0xf]);
> + }
> + g_free(result);
> + qcrypto_hash_free(hash);
Drop these two frees.
> + }
> +}
> +
> int main(int argc, char **argv)
> {
> int ret = qcrypto_init(&error_fatal);
> @@ -252,5 +299,6 @@ int main(int argc, char **argv)
> g_test_add_func("/crypto/hash/prealloc", test_hash_prealloc);
> g_test_add_func("/crypto/hash/digest", test_hash_digest);
> g_test_add_func("/crypto/hash/base64", test_hash_base64);
> + g_test_add_func("/crypto/hash/accumulate", test_hash_accumulate);
> return g_test_run();
> }
> --
> 2.34.1
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-08-08 17:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 19:51 [PATCH v4 00/15] hw/misc/aspeed_hace: Fix SG Accumulative Hash Calculations Alejandro Zeise
2024-08-07 19:51 ` [PATCH v4 01/15] crypto: accumulative hashing API Alejandro Zeise
2024-08-08 16:04 ` Daniel P. Berrangé
2024-08-08 17:00 ` Markus Armbruster
2024-08-07 19:51 ` [PATCH v4 02/15] crypto/hash-glib: Implement new hash API Alejandro Zeise
2024-08-08 16:58 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 03/15] crypto/hash-gcrypt: " Alejandro Zeise
2024-08-08 17:00 ` Daniel P. Berrangé
2024-08-08 17:05 ` Daniel P. Berrangé
2024-08-08 18:24 ` Alejandro Zeise
2024-08-09 8:37 ` Daniel P. Berrangé
2024-08-08 17:10 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 04/15] crypto/hash-gnutls: " Alejandro Zeise
2024-08-08 17:10 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 05/15] crypto/hash-nettle: " Alejandro Zeise
2024-08-07 19:51 ` [PATCH v4 06/15] crypto/hash-afalg: " Alejandro Zeise
2024-08-08 17:16 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 07/15] crypto/hash: Implement and use " Alejandro Zeise
2024-08-08 16:21 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 08/15] tests/unit/test-crypto-hash: accumulative hashing Alejandro Zeise
2024-08-08 17:18 ` Daniel P. Berrangé [this message]
2024-08-07 19:51 ` [PATCH v4 09/15] crypto/hash-glib: Remove old hash API functions Alejandro Zeise
2024-08-08 17:19 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 10/15] crypto/hash-gcrypt: " Alejandro Zeise
2024-08-08 17:19 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 11/15] crypto/hash-gnutls: " Alejandro Zeise
2024-08-08 17:20 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 12/15] crypto/hash-nettle: " Alejandro Zeise
2024-08-08 17:22 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 13/15] crypto/hash-afalg: " Alejandro Zeise
2024-08-08 17:23 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 14/15] crypto/hashpriv: Remove old hash API function Alejandro Zeise
2024-08-08 17:24 ` Daniel P. Berrangé
2024-08-07 19:51 ` [PATCH v4 15/15] hw/misc/aspeed_hace: Fix SG Accumulative hashing Alejandro Zeise
2024-08-27 13:53 ` Cédric Le Goater
2024-08-07 20:01 ` [PATCH v4 00/15] hw/misc/aspeed_hace: Fix SG Accumulative Hash Calculations Philippe Mathieu-Daudé
2024-08-07 20:30 ` Alejandro Zeise
2024-08-08 8:46 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrT972O-HcxMkT9L@redhat.com \
--to=berrange@redhat.com \
--cc=alejandro.zeise@seagate.com \
--cc=clg@kaod.org \
--cc=evan.burgess@seagate.com \
--cc=jonathan.henze@seagate.com \
--cc=kris.conklin@seagate.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).