From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, linux-crypto@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] crypto: testmgr - Add test vectors for authenc(hmac(md5),cbc(aes))
Date: Fri, 27 Mar 2026 18:03:48 +0100 [thread overview]
Message-ID: <c2a3dc2e-8d4a-4a59-ac5a-ca22be705488@wp.pl> (raw)
In-Reply-To: <abToanZh-mkEjmJ-@gondor.apana.org.au>
Hi Herbert,
On 14/03/2026 05:47, Herbert Xu wrote:
> On Tue, Mar 03, 2026 at 07:48:44PM +0100, Aleksander Jan Bajkowski wrote:
>> Test vectors were generated starting from existing CBC(AES) test vectors
>> (RFC3602, NIST SP800-38A) and adding HMAC(MD5) computed with Python
>> script. Then, the results were double-checked on Mediatek MT7981 (safexcel)
>> and NXP P2020 (talitos). Both platforms pass self-tests.
>>
>> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
>> ---
>> v4:
>> - rename aes-generic -> aes-lib
>> v3:
>> - correct sha384 -> md5 in description
>> v2:
>> - rebase and resolve conflicts
>> ---
>> crypto/testmgr.c | 7 ++
>> crypto/testmgr.h | 255 +++++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 262 insertions(+)
> The previous patch has already been applied. Please redo this
> as an incremental patch.
Checked the crypto tree, and this patch still isn't applied. I've sent
multiple test vectors, and you're probably referring to a another patch.
Should I send it again, or will you accept it as is?
By the way, that's the last one. As of now, all my routers have the
missing vectors added :)
Regards, Aleksander
next prev parent reply other threads:[~2026-03-27 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 18:48 [PATCH v4] crypto: testmgr - Add test vectors for authenc(hmac(md5),cbc(aes)) Aleksander Jan Bajkowski
2026-03-14 4:47 ` Herbert Xu
2026-03-27 17:03 ` Aleksander Jan Bajkowski [this message]
2026-03-30 8:46 ` Herbert Xu
2026-04-03 1:03 ` Herbert Xu
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=c2a3dc2e-8d4a-4a59-ac5a-ca22be705488@wp.pl \
--to=olek2@wp.pl \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.