From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: arm/blake2b - Set FINAL_NONZERO
Date: Fri, 25 Apr 2025 12:42:17 +0200 [thread overview]
Message-ID: <aAtnCR5jVAnjfR1i@Red> (raw)
In-Reply-To: <aAsCk3jtbAE7dPpJ@gondor.apana.org.au>
Le Fri, Apr 25, 2025 at 11:33:39AM +0800, Herbert Xu a écrit :
> On Thu, Apr 24, 2025 at 10:39:09PM +0200, Corentin Labbe wrote:
> >
> > Thanks it fixes my crypto hw devices.
> > So Tested-by: Corentin LABBE <clabbe.montjoie@gmail.com>
>
> What about the sha1-ce failure on arm64? Did that go away too?
No they are still there:
[ 2.022921] alg: shash: sha1-ce test failed (wrong result) on test vector 0, cfg="init+update+final aligned buffer"
[ 2.022950] alg: self-tests for sha1 using sha1-ce failed (rc=-22)
[ 2.022957] ------------[ cut here ]------------
[ 2.022960] alg: self-tests for sha1 using sha1-ce failed (rc=-22)
[ 2.023009] WARNING: CPU: 3 PID: 110 at crypto/testmgr.c:5871 alg_test+0x5e8/0x60c
[ 2.023033] Modules linked in:
[ 2.023046] CPU: 3 UID: 0 PID: 110 Comm: cryptomgr_test Not tainted 6.15.0-rc1-g583d02477052 #2 PREEMPT
Setting prompt string to ['-+\\[ end trace \\w* \\]-+[^\\n]*\\r', '/ #', '~ #', 'sh-5.1#', 'Login timed out', 'Login incorrect']
[ 2.023057] Hardware name: Pine64 PINE H64 Model A (DT)
[ 2.023062] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.023071] pc : alg_test+0x5e8/0x60c
[ 2.023081] lr : alg_test+0x5e8/0x60c
[ 2.023090] sp : ffff80008180bd40
[ 2.023093] x29: ffff80008180bde0 x28: 00000000000000bc x27: 0000000000000000
[ 2.023106] x26: 00000000ffffffff x25: 00000000ffffffea x24: 0000000000000177
[ 2.023118] x23: ffff800081014208 x22: ffff00000152ae80 x21: 000000000500000e
[ 2.023130] x20: ffff00000152ae00 x19: ffff800080a26238 x18: 00000000fffffffe
[ 2.023142] x17: 2c3020726f746365 x16: 762074736574206e x15: ffff800080fdc47b
[ 2.023154] x14: 0000000000000000 x13: ffff800080fdc47f x12: 65742d666c657320
[ 2.023165] x11: 0000000000000058 x10: 0000000000000029 x9 : 0000000000000001
[ 2.023177] x8 : ffff800080ec3308 x7 : ffff80008180bae0 x6 : 000000000000000c
[ 2.023188] x5 : 0000000000000000 x4 : 00000000fffff0b5 x3 : 0000000000000000
[ 2.023199] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000099a7000
[ 2.023211] Call trace:
[ 2.023216] alg_test+0x5e8/0x60c (P)
[ 2.023229] cryptomgr_test+0x24/0x44
[ 2.023240] kthread+0x12c/0x204
[ 2.023253] ret_from_fork+0x10/0x20
[ 2.023267] ---[ end trace 0000000000000000 ]---
>
> That didn't seem related to crypto_engine.
>
> > But I still got some crash with blake2b:
> > +[ 54.348477] alg: shash: blake2b-256-neon test failed (wrong result) on test vector 1, cfg="init+update+final aligned buffer"
> > +[ 54.348525] alg: self-tests for blake2b-256 using blake2b-256-neon failed (rc=-22)
> > +[ 54.348536] ------------[ cut here ]------------
>
> OK this is easy, I left out the FINAL_NONZERO bit in the arm patch:
>
blake2b crash disappear, so
Tested-by: Corentin LABBE <clabbe.montjoie@gmail.com>
Thanks
next prev parent reply other threads:[~2025-04-25 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 12:09 all crypto selftests failed on linux-next-20250424 Corentin Labbe
2025-04-24 13:14 ` Herbert Xu
2025-04-24 14:42 ` [PATCH] crypto: Remove CRYPTO_ALG_ENGINE bit Herbert Xu
2025-04-24 20:39 ` Corentin Labbe
2025-04-25 3:33 ` [PATCH] crypto: arm/blake2b - Set FINAL_NONZERO Herbert Xu
2025-04-25 10:42 ` Corentin Labbe [this message]
2025-04-25 10:58 ` [PATCH] crypto: arm64/sha1 - Set finalize for short finup Herbert Xu
2025-04-25 19:16 ` Corentin Labbe
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=aAtnCR5jVAnjfR1i@Red \
--to=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.