From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: all crypto selftests failed on linux-next-20250424
Date: Thu, 24 Apr 2025 14:09:34 +0200 [thread overview]
Message-ID: <aAop_uMhxVh2l5Fy@Red> (raw)
Hello
All crypto selftests failed on top of linux-next-20250424
Example on x86_64:
[ 4.637589] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ 4.637822] #PF: supervisor instruction fetch in kernel mode
[ 4.637931] #PF: error_code(0x0010) - not-present page
[ 4.638166] PGD 0 P4D 0
[ 4.638359] Oops: Oops: 0010 [#1] SMP NOPTI
[ 4.638808] CPU: 0 UID: 0 PID: 64 Comm: virtio1-engine Not tainted 6.15.0-rc1-g63dc06cd12f9 #1 PREEMPT(voluntary)
[ 4.639068] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-20240910_120124-localhost 04/01/2014
[ 4.639338] RIP: 0010:0x0
[ 4.640112] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 4.640253] RSP: 0018:ffffb2d8c025fe68 EFLAGS: 00010202
[ 4.640451] RAX: 0000000000000000 RBX: ffffa1d009a937b0 RCX: ffffa1d009a93768
[ 4.640579] RDX: ffffa1d009a93768 RSI: ffffa1d009b10920 RDI: ffffa1d009a93728
[ 4.640706] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000055
[ 4.640829] R10: 0000000000000000 R11: 000000000000004b R12: ffffa1d009a93760
[ 4.640952] R13: ffffa1d009b10920 R14: ffffa1d009a93768 R15: 0000000000000282
[ 4.641126] FS: 0000000000000000(0000) GS:ffffa1d0c0efe000(0000) knlGS:0000000000000000
[ 4.641272] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4.641379] CR2: ffffffffffffffd6 CR3: 0000000017e32000 CR4: 00000000000006f0
[ 4.641592] Call Trace:
[ 4.642112] <TASK>
[ 4.642234] crypto_pump_work+0x151/0x290
[ 4.642693] ? __pfx_crypto_pump_work+0x10/0x10
[ 4.642780] kthread_worker_fn+0x94/0x250
[ 4.642860] ? __pfx_kthread_worker_fn+0x10/0x10
[ 4.642942] kthread+0xf6/0x1f0
[ 4.643003] ? __pfx_kthread+0x10/0x10
[ 4.643086] ret_from_fork+0x2f/0x50
[ 4.643163] ? __pfx_kthread+0x10/0x10
[ 4.643234] ret_from_fork_asm+0x1a/0x30
[ 4.643345] </TASK>
[ 4.643434] Modules linked in:
[ 4.643615] CR2: 0000000000000000
[ 4.643899] ---[ end trace 0000000000000000 ]---
[ 4.644059] RIP: 0010:0x0
[ 4.644128] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 4.644240] RSP: 0018:ffffb2d8c025fe68 EFLAGS: 00010202
[ 4.644330] RAX: 0000000000000000 RBX: ffffa1d009a937b0 RCX: ffffa1d009a93768
[ 4.644449] RDX: ffffa1d009a93768 RSI: ffffa1d009b10920 RDI: ffffa1d009a93728
[ 4.644561] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000055
[ 4.644672] R10: 0000000000000000 R11: 000000000000004b R12: ffffa1d009a93760
[ 4.644783] R13: ffffa1d009b10920 R14: ffffa1d009a93768 R15: 0000000000000282
[ 4.644894] FS: 0000000000000000(0000) GS:ffffa1d0c0efe000(0000) knlGS:0000000000000000
[ 4.645019] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4.645142] CR2: ffffffffffffffd6 CR3: 0000000017e32000 CR4: 00000000000006f0
[ 4.645326] note: virtio1-engine[64] exited with irqs disabled
Example for arm
[ 0.293756] alg: self-tests for sha1 using sha1-ce failed (rc=-22)
[ 0.293762] ------------[ cut here ]------------
[ 0.293766] alg: self-tests for sha1 using sha1-ce failed (rc=-22)
[ 0.293809] WARNING: CPU: 7 PID: 104 at crypto/testmgr.c:5871 alg_test+0x5e4/0x608
[ 0.293833] Modules linked in:
[ 0.293844] CPU: 7 UID: 0 PID: 104 Comm: cryptomgr_test Not tainted 6.15.0-rc3-next-20250424-00005-g954547706c5d #8 PREEMPT
[ 0.293856] Hardware name: Radxa A5E (DT)
[ 0.293861] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 0.293871] pc : alg_test+0x5e4/0x608
[ 0.293882] lr : alg_test+0x5e4/0x608
[ 0.293893] sp : ffff80008175bd40
[ 0.293896] x29: ffff80008175bde0 x28: 00000000000000bc x27: 0000000000000000
[ 0.293911] x26: 00000000ffffffff x25: ffff800080fe1f58 x24: 00000000ffffffea
[ 0.293925] x23: 0000000000000177 x22: ffff0000c202de80 x21: 000000000500000e
[ 0.293939] x20: ffff0000c202de00 x19: ffff800080a05710 x18: 00000000fffffffe
[ 0.294032] Call trace:
[ 0.294036] alg_test+0x5e4/0x608 (P)
[ 0.294051] cryptomgr_test+0x24/0x44
[ 0.294063] kthread+0x12c/0x204
Regards
next reply other threads:[~2025-04-24 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 12:09 Corentin Labbe [this message]
2025-04-24 13:14 ` all crypto selftests failed on linux-next-20250424 Herbert Xu
2025-04-24 14:42 ` [PATCH] crypto: Remove CRYPTO_ALG_ENGINE bit Herbert Xu
2025-04-24 20:39 ` Corentin Labbe
2025-04-25 3:33 ` [PATCH] crypto: arm/blake2b - Set FINAL_NONZERO Herbert Xu
2025-04-25 10:42 ` Corentin Labbe
2025-04-25 10:58 ` [PATCH] crypto: arm64/sha1 - Set finalize for short finup Herbert Xu
2025-04-25 19:16 ` Corentin Labbe
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=aAop_uMhxVh2l5Fy@Red \
--to=clabbe.montjoie@gmail.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