From: "Paul Louvel" <paul.louvel@bootlin.com>
To: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Paul Louvel" <paul.louvel@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Christophe Leroy" <chleroy@kernel.org>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 01/19] crypto: talitos/hash - Use CRYPTO_AHASH_BLOCK_ONLY API
Date: Wed, 15 Jul 2026 07:50:47 +0200 [thread overview]
Message-ID: <DJYWRQ3SZ407.7CA8QWJ5UVRM@bootlin.com> (raw)
In-Reply-To: <akdiMro0yKwwicaa@gondor.apana.org.au>
On Fri Jul 3, 2026 at 9:18 AM CEST, Herbert Xu wrote:
> On Thu, Jun 11, 2026 at 09:35:55AM +0200, Paul Louvel wrote:
>>
>> @@ -2932,8 +2861,11 @@ static struct talitos_alg_template driver_algs[] = {
>> .cra_name = "md5",
>> .cra_driver_name = "md5-talitos",
>> .cra_blocksize = MD5_HMAC_BLOCK_SIZE,
>> + .cra_reqsize = sizeof(struct talitos_ahash_req_ctx),
>> .cra_flags = CRYPTO_ALG_ASYNC |
>> - CRYPTO_ALG_ALLOCATES_MEMORY,
>> + CRYPTO_ALG_ALLOCATES_MEMORY |
>> + CRYPTO_AHASH_ALG_BLOCK_ONLY |
>> + CRYPTO_AHASH_ALG_FINAL_NONZERO,
>
> Sorry, but the FINAL_NONZERO flag doesn't work for algorithms like
> md5.
>
> The reason is that all implementations of md5 must accept the exports
> from each other. So as long as the generic md5 doesn't not set
> FINAL_NONZERO, your driver will need to be able to take that on
> import.
>
> Cheers,
Hi Herbert,
Thanks for the info.
Paul.
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-15 5:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 7:35 [PATCH v2 00/19] crypto: talitos - Driver cleanup Paul Louvel
2026-06-11 7:35 ` [PATCH v2 01/19] crypto: talitos/hash - Use CRYPTO_AHASH_BLOCK_ONLY API Paul Louvel
2026-07-03 7:18 ` Herbert Xu
2026-07-15 5:50 ` Paul Louvel [this message]
2026-06-11 7:35 ` [PATCH v2 02/19] crypto: talitos - Move driver into dedicated directory Paul Louvel
2026-06-11 7:35 ` [PATCH v2 03/19] crypto: talitos - Add missing includes to driver header file Paul Louvel
2026-06-11 7:35 ` [PATCH v2 04/19] crypto: talitos/hwrng - Move into separate file Paul Louvel
2026-06-11 7:35 ` [PATCH v2 05/19] crypto: talitos - Prepare crypto implementation file splitting Paul Louvel
2026-06-11 7:36 ` [PATCH v2 06/19] crypto: talitos/hash - Move into separate file Paul Louvel
2026-06-11 7:36 ` [PATCH v2 07/19] crypto: talitos/skcipher " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 08/19] crypto: talitos/aead " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 09/19] crypto: talitos/hash - Convert to {init,exit}_tfm type-specific API Paul Louvel
2026-06-11 7:36 ` [PATCH v2 10/19] crypto: talitos/skcipher " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 11/19] crypto: talitos/aead " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 12/19] crypto: talitos/hash - Use macro for algorithm definitions Paul Louvel
2026-06-11 7:36 ` [PATCH v2 13/19] crypto: talitos/skcipher " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 14/19] crypto: talitos/aead " Paul Louvel
2026-06-11 7:36 ` [PATCH v2 15/19] crypto: talitos - Remove alg settings in talitos_register_common() Paul Louvel
2026-06-11 7:36 ` [PATCH v2 16/19] crypto: talitos - Introduce is_sec1() helper with static key support Paul Louvel
2026-06-11 7:36 ` [PATCH v2 17/19] crypto: talitos - Replace has_ftr_sec1() with is_sec1() static key helper Paul Louvel
2026-06-11 7:36 ` [PATCH v2 18/19] crypto: talitos - Introduce per-SEC-version descriptor and pointer structures Paul Louvel
2026-06-11 7:36 ` [PATCH v2 19/19] crypto: talitos - Remove TALITOS_DESC_SIZE macro Paul Louvel
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=DJYWRQ3SZ407.7CA8QWJ5UVRM@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=chleroy@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=herve.codina@bootlin.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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
Powered by JetHome