From: Ingo Franzki <ifranzki@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Eric Biggers <ebiggers@kernel.org>,
Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>,
linux-crypto@vger.kernel.org
Subject: Sporadic errors with alg selftest on next kernel.
Date: Mon, 19 May 2025 10:09:10 +0200 [thread overview]
Message-ID: <35642f32-68ae-4064-9055-a4e1d8965257@linux.ibm.com> (raw)
Hi Herbert,
besides the regression found in paes-crt on s390x (reported and analyzed by Harald already), we sporadically encounter additional strange failures in our CI on the next kernel:
During this weekend's CI run, we got the following:
alg: aead: error allocating gcm_base(ctr(aes-generic),ghash-generic) (generic impl of gcm(aes)): -17
alg: self-tests for gcm(aes) using gcm-aes-s390 failed (rc=-17)
Last week, we had a similar failure:
aes_s390: Allocating AES fallback algorithm ctr(aes) failed
alg: skcipher: failed to allocate transform for ctr-aes-s390: -17
alg: self-tests for ctr(aes) using ctr-aes-s390 failed (rc=-17)
Those are only single failures, not reproducible, happen only of one system, although the same code is run on multiple systems.
So it must be some kind a race condition...
-17 is EEXIST, and from a quick look into the code this might be coming from registering an alg (e.g. __crypto_register_alg(), crypto_register_template(), af_alg_register_type(), crypto_add_alg()) when the alg is already there....
So looks like one wants to register the same alg although it was already registered concurrently?
Note that the s390x-AES ciphers are usually added via module_cpu_feature_match() automatically.
Maybe a selftest run attempts to add them again while or during aes_s390_init() is about to add them as well?
Its hard to debug, since it only happens sporadically and can't be reproduced easily.
Any idea where this might come from?
We did not see these kind of errors since long time, and still don't see them on kernels other than next.
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-05-19 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 8:09 Ingo Franzki [this message]
2025-05-19 8:28 ` Sporadic errors with alg selftest on next kernel Herbert Xu
2025-05-19 8:34 ` Herbert Xu
2025-05-19 8:43 ` Ingo Franzki
2025-05-19 9:34 ` Herbert Xu
2025-05-19 10:29 ` [PATCH] crypto: api - Redo lookup on EEXIST Herbert Xu
2025-05-19 13:47 ` Ingo Franzki
2025-05-26 6:44 ` Ingo Franzki
2025-05-26 8:13 ` 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=35642f32-68ae-4064-9055-a4e1d8965257@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox