From: Erhard Furtner <erhard_f@mailbox.org>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: WARNING: CPU: 1 PID: 81 at crypto/testmgr.c:5931 alg_test+0x2a4/0x300 (Thinkpad T60, v6.12-rc2)
Date: Tue, 15 Oct 2024 20:08:50 +0200 [thread overview]
Message-ID: <20241015200850.6a1d0e2e@yea> (raw)
In-Reply-To: <20241010013829.68da351d@yea>
On Thu, 10 Oct 2024 01:38:29 +0200
Erhard Furtner <erhard_f@mailbox.org> wrote:
> On kernel v6.12-rc2 this warning shows up at boot on my Thinkpad T60:
>
> [...]
> alg: akcipher: decrypt test failed. err -1
> alg: akcipher: test 1 failed for rsa-generic, err=-1
> alg: self-tests for rsa using rsa-generic failed (rc=-1)
> ------------[ cut here ]------------
> alg: self-tests for rsa using rsa-generic failed (rc=-1)
> WARNING: CPU: 1 PID: 81 at crypto/testmgr.c:5931 alg_test+0x2a4/0x300
> Modules linked in:
> CPU: 1 UID: 0 PID: 81 Comm: cryptomgr_test Not tainted 6.12.0-rc2-P3 #3
> Hardware name: LENOVO 2007F2G/2007F2G, BIOS 79ETE7WW (2.27 ) 03/21/2011
> EIP: alg_test+0x2a4/0x300
> Code: 53 68 0b 27 9a c9 e8 e3 7f 3e 00 83 c4 10 89 f0 be fe ff ff ff 83 ff fe 74 9b 57 50 53 68 cd 80 9a c9 e8 37 a2 cb ff 83 c4 10 <0f> 0b 89 fe eb 85 68 ef 66 95 c9 53 56 68 ce 89 9b c9 e8 7d 7d 3e
> EAX: 00000000 EBX: c1d2fa80 ECX: 00000000 EDX: 00000000
> ESI: fffffffe EDI: ffffffff EBP: c1a4bf60 ESP: c1a4bec8
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010282
> CR0: 80050033 CR2: 00000000 CR3: 09b7c000 CR4: 000006f0
> Call Trace:
> ? show_regs+0x4e/0x5c
> ? __warn+0x87/0xdc
> ? alg_test+0x2a4/0x300
> ? report_bug+0x94/0x108
> ? exc_overflow+0x3c/0x3c
> ? handle_bug+0x41/0x60
> ? exc_invalid_op+0x17/0x40
> ? handle_exception+0x101/0x101
> ? exc_overflow+0x3c/0x3c
> ? alg_test+0x2a4/0x300
> ? exc_overflow+0x3c/0x3c
> ? alg_test+0x2a4/0x300
> ? __switch_to_asm+0x88/0xe4
> ? __switch_to_asm+0x82/0xe4
> ? __switch_to_asm+0x7c/0xe4
> ? __switch_to_asm+0x76/0xe4
> ? __switch_to_asm+0x70/0xe4
> ? __switch_to_asm+0x6a/0xe4
> ? __switch_to_asm+0x64/0xe4
> ? __switch_to_asm+0x5e/0xe4
> ? __switch_to_asm+0x58/0xe4
> ? __switch_to_asm+0x52/0xe4
> ? __switch_to_asm+0x4c/0xe4
> ? __switch_to_asm+0x46/0xe4
> ? _raw_spin_unlock+0x8/0xc
> ? finish_task_switch+0x98/0x244
> ? __switch_to_asm+0x1c/0xe4
> ? __switch_to_asm+0x16/0xe4
> ? __schedule+0x587/0x7a4
> cryptomgr_test+0x1c/0x38
> kthread+0xc4/0xd0
> ? crypto_alg_put+0x40/0x40
> ? kthread_blkcg+0x24/0x24
> ? kthread_blkcg+0x24/0x24
> ret_from_fork+0x31/0x3c
> ret_from_fork_asm+0x12/0x18
> entry_INT80_32+0xf0/0xf0
> ---[ end trace 0000000000000000 ]---
v6.12-rc3 still affected. So I bisected the issue to the following commit:
# git bisect good
5a72a244bac3e8663834d88bb0b4f9069203e5e0 is the first bad commit
commit 5a72a244bac3e8663834d88bb0b4f9069203e5e0
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sat Aug 10 14:21:02 2024 +0800
crypto: rsa - Check MPI allocation errors
Fixes: 6637e11e4ad2 ("crypto: rsa - allow only odd e and restrict value in FIPS mode")
Fixes: f145d411a67e ("crypto: rsa - implement Chinese Remainder Theorem for faster private key operation")
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto/rsa.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
Reverting 5a72a244bac3e8663834d88bb0b4f9069203e5e0 on top of v6.12-rc3 fixes the failure.
Regards,
Erhard
next prev parent reply other threads:[~2024-10-15 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 23:38 WARNING: CPU: 1 PID: 81 at crypto/testmgr.c:5931 alg_test+0x2a4/0x300 (Thinkpad T60, v6.12-rc2) Erhard Furtner
2024-10-15 18:08 ` Erhard Furtner [this message]
2024-10-16 5:36 ` Herbert Xu
2024-10-16 14:08 ` Erhard Furtner
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=20241015200850.6a1d0e2e@yea \
--to=erhard_f@mailbox.org \
--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;
as well as URLs for NNTP newsgroup(s).