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: Re: Sporadic errors with alg selftest on next kernel.
Date: Mon, 19 May 2025 10:43:29 +0200 [thread overview]
Message-ID: <cf467fd7-fa25-4ac0-9570-a5f0e20d1fbb@linux.ibm.com> (raw)
In-Reply-To: <aCrtDPVJwK6SAN6b@gondor.apana.org.au>
On 19.05.2025 10:34, Herbert Xu wrote:
> On Mon, May 19, 2025 at 10:09:10AM +0200, Ingo Franzki wrote:
>>
>> We did not see these kind of errors since long time, and still don't see them on kernels other than next.
>
> Could you check whether the CI runs have the extra testing enabled
> for non-next kernels? If they actually had extra tests enabled before
> the current next kernel then that would be surprising.
No we do not explicitly enable the extra tests, neither on non-next kernels, nor on next kernels.
So it can very well be that enabling the extra tests by default now triggers the failures to show up.
>
> Cheers,
--
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 prev parent reply other threads:[~2025-05-19 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 8:09 Sporadic errors with alg selftest on next kernel Ingo Franzki
2025-05-19 8:28 ` Herbert Xu
2025-05-19 8:34 ` Herbert Xu
2025-05-19 8:43 ` Ingo Franzki [this message]
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=cf467fd7-fa25-4ac0-9570-a5f0e20d1fbb@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