From: Ingo Franzki <ifranzki@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, ebiggers@kernel.org,
freude@linux.ibm.com, dengler@linux.ibm.com
Subject: CI: Another strange crypto message in syslog
Date: Thu, 5 Jun 2025 13:26:34 +0200 [thread overview]
Message-ID: <d4520a75-c765-406b-a115-a79bbdf8d199@linux.ibm.com> (raw)
Hi Herbert,
we see the following error messages in syslog on the current next kernel:
Jun 05 13:15:20 a35lp62.lnxne.boe kernel: basic hdkf test(hmac(sha256)): failed to allocate transform: -2
Jun 05 13:15:20 a35lp62.lnxne.boe kernel: alg: full crypto tests enabled. This is intended for developer use only.
The first one seem to be failure, but I can't tell where..... I don't see any other typical selftest failure messages.
-1 is ENOENT. It might be related to the recent changes with sha256 being now in a library...
The second one is probably because the full selftests are now enabled by default. Does it make sense to output this message now anymore at all?
Kind regards,
Ingo
--
Ingo Franzki
eMail: ifranzki@linux.ibm.com
Tel: ++49 (0)7031-16-4648
Linux on IBM Z Development, Schoenaicher Str. 220, 71032 Boeblingen, Germany
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM DATA Privacy Statement: https://www.ibm.com/privacy/us/en/
next reply other threads:[~2025-06-05 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:26 Ingo Franzki [this message]
2025-06-05 14:26 ` CI: Another strange crypto message in syslog Eric Biggers
2025-06-06 7:19 ` Harald Freudenberger
2025-06-06 17:45 ` Eric Biggers
2025-06-16 10:50 ` Harald Freudenberger
2025-06-16 15:58 ` Eric Biggers
2025-06-10 12:37 ` Ingo Franzki
2025-06-10 19:16 ` [PATCH] crypto: hkdf - move to late_initcall Eric Biggers
2025-06-11 3: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=d4520a75-c765-406b-a115-a79bbdf8d199@linux.ibm.com \
--to=ifranzki@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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.