From: Stephan Mueller <smueller@chronox.de>
To: David Gstir <david@sigma-star.at>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
linux-kernel@vger.kernel.org, Richard Weinberger <richard@nod.at>
Subject: Re: Can an ahash driver be used through shash API?
Date: Wed, 29 May 2019 16:18:18 +0200 [thread overview]
Message-ID: <4256916.YlTHG9RRyR@tauon.chronox.de> (raw)
In-Reply-To: <729A4150-93A0-456B-B7AB-6D3A446E600E@sigma-star.at>
Am Mittwoch, 29. Mai 2019, 16:04:47 CEST schrieb David Gstir:
Hi David,
> Hi!
>
> I've done some testing with hardware acceleration of hash functions
> and noticed that, when using the synchronous message digest API (shash),
> some drivers are not usable. In my case the CAAM driver for SHA256.
> Using the asynchronous interface (ahash), everything works as expected.
> Looking at the driver source, the CAAM driver only implements the ahash
> interface.
>
> I'm wondering if there a way to use an ahash driver through the shash
> interface?
Short: no.
>
> I've seen that it does actually work the other way around, since
> crypto_init_shash_ops_async() in crypto/shash.c takes care of translating
> calls from ahash to shash and that's how the *-generic drivers are usable
> through the ahash API.
The crypto_alloc_shash will only identify cipher implementations that were
registered with the CRYPTO_ALG_TYPE_SHASH flag. That flag is set when a cipher
is registered using crypto_register_shash.
Thus, ciphers registered with crypto_register_ahash will not bear this flag
and thus will not be found by the allocation function.
Ciao
Stephan
next prev parent reply other threads:[~2019-05-29 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 14:04 David Gstir
2019-05-29 14:18 ` Stephan Mueller [this message]
2019-05-29 20:21 ` Richard Weinberger
2019-05-30 5:38 ` Stephan Mueller
2019-05-30 10:02 ` Pascal Van Leeuwen
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=4256916.YlTHG9RRyR@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=david@sigma-star.at \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®