qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alejandro Zeise <alejandro.zeise@seagate.com>
Cc: "qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
	Kris Conklin <kris.conklin@seagate.com>,
	Jonathan Henze <jonathan.henze@seagate.com>,
	Evan Burgess <evan.burgess@seagate.com>,
	"clg@kaod.org" <clg@kaod.org>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v4 03/15] crypto/hash-gcrypt: Implement new hash API
Date: Fri, 9 Aug 2024 09:37:27 +0100	[thread overview]
Message-ID: <ZrXVR95hnQwg5zGh@redhat.com> (raw)
In-Reply-To: <LV8PR20MB6853CD119297E25B2218EC9FEFB92@LV8PR20MB6853.namprd20.prod.outlook.com>

On Thu, Aug 08, 2024 at 06:24:10PM +0000, Alejandro Zeise wrote:
> > On Wed, Aug 07, 2024 at 07:51:10PM +0000, Alejandro Zeise wrote:
> > > Implements the new hashing API in the gcrypt hash driver.
> > > Supports creating/destroying a context, updating the context with 
> > > input data and obtaining an output hash.
> > >
> > > Signed-off-by: Alejandro Zeise <alejandro.zeise@seagate.com>
> > > ---
> > >  crypto/hash-gcrypt.c | 79 
> > > ++++++++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 79 insertions(+)
> > >
> > > diff --git a/crypto/hash-gcrypt.c b/crypto/hash-gcrypt.c index 
> > > 829e48258d..e05511cafa 100644
> > > --- a/crypto/hash-gcrypt.c
> > > +++ b/crypto/hash-gcrypt.c
> > > @@ -1,6 +1,7 @@
> > >  /*
> > >   * QEMU Crypto hash algorithms
> > >   *
> > > + * Copyright (c) 2024 Seagate Technology LLC and/or its Affiliates
> > >   * Copyright (c) 2016 Red Hat, Inc.
> > >   *
> > >   * This library is free software; you can redistribute it and/or @@ 
> > > -110,7 +111,85 @@ qcrypto_gcrypt_hash_bytesv(QCryptoHashAlgorithm alg,
> > >      return -1;
> > >  }
> > >
> > > +static
> > > +QCryptoHash *qcrypto_gcrypt_hash_new(QCryptoHashAlgorithm alg, Error 
> > > +**errp) {
> > > +    QCryptoHash *hash = NULL;
> > > +
> > > +    if (!qcrypto_hash_supports(alg)) {
> > > +        error_setg(errp,
> > > +                   "Unknown hash algorithm %d",
> > > +                   alg);
> > > +    } else {
> > > +        hash = g_new(QCryptoHash, 1);
> > > +        hash->alg = alg;
> > > +        hash->opaque = g_new(gcry_md_hd_t, 1);
> > > +
> > > +        gcry_md_open((gcry_md_hd_t *) hash->opaque, qcrypto_hash_alg_map[alg], 0);
> > > +    }
> > > +
> > > +    return hash;
> > > +}
> > > +
> > > +static
> > > +void qcrypto_gcrypt_hash_free(QCryptoHash *hash) {
> > > +    gcry_md_hd_t *ctx = hash->opaque;
> > > +
> > > +    if (ctx) {
> > > +        gcry_md_close(*ctx);
> > > +        g_free(ctx);
> > > +    }
> > > +
> > > +    g_free(hash);
> > > +}
> > > +
> > > +
> > > +static
> > > +int qcrypto_gcrypt_hash_update(QCryptoHash *hash,
> > > +                               const struct iovec *iov,
> > > +                               size_t niov,
> > > +                               Error **errp) {
> > > +    gcry_md_hd_t *ctx = hash->opaque;
> > > +
> > > +    for (int i = 0; i < niov; i++) {
> > > +        gcry_md_write(*ctx, iov[i].iov_base, iov[i].iov_len);
> >
> >   int ret = gcry_md_write(*ctx, iov[i].iov_base, iov[i].iov_len);
> >   if (ret != 0) {
> >       error_setg(....)
> >       return -1;
> >   }
> >
> >
> > With regards,
> > Daniel
> 
> gcry_md_write() is declared as void which is why I had no error variable present.

Opps, yes, I'm getting confused with the other APIs.


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 :|



  reply	other threads:[~2024-08-09  8:38 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é [this message]
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é
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=ZrXVR95hnQwg5zGh@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).