The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ryan Wanner <ryan.wanner@microchip.com>
To: <linux-crypto@vger.kernel.org>, open list <linux-kernel@vger.kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Subject: crypto self-test errors kernel 6.12.4
Date: Tue, 6 May 2025 13:12:31 -0700	[thread overview]
Message-ID: <468a8e17-d564-441d-9893-72b0ed48d8bb@microchip.com> (raw)

Hello,

I upgraded my ARM kernel from v6.6.9 to v6.12.4 and I am seeing some
crypto self test errors that I did not see before. Shown below. These
errors are different every boot and I did not see them on 6.6.9 kernel.
I did notice that when I compile the crypto HW acceleration drivers as
modules like this:
CONFIG_CRYPTO_DEV_ATMEL_AES [=m]
CONFIG_CRYPTO_DEV_ATMEL_TDES [=m]
CONFIG_CRYPTO_DEV_ATMEL_SHA [=m]

and have them loaded by systemd at boot I do not get errors and all the
self tests pass.

Is there a race condition I am not aware of? Or is the new asynchronous
crypto tests creating bugs in the HW acceleration drivers.


DRBG: could not allocate digest TFM handle: hmac(sha512)
alg: drbg: Failed to reset rng
alg: drbg: Test 0 failed for drbg_nopr_hmac_sha512
alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 90 at crypto/testmgr.c:5928 0xc0397fd0
alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)

alg: hash: error allocating hmac(sha512-generic) (generic impl of
hmac(sha512)): -17
alg: self-tests for hmac(sha512) using atmel-hmac-sha512 failed (rc=-17)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 53 at crypto/testmgr.c:5928 0xc0397fd0
alg: self-tests for hmac(sha512) using atmel-hmac-sha512 failed (rc=-17)


Best,
Ryan

             reply	other threads:[~2025-05-06 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 20:12 Ryan Wanner [this message]
2025-05-07  0:53 ` crypto self-test errors kernel 6.12.4 Herbert Xu
2025-05-07 15:27   ` Ryan Wanner
2025-05-08  5:07     ` 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=468a8e17-d564-441d-9893-72b0ed48d8bb@microchip.com \
    --to=ryan.wanner@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox