[SRU][N][PATCH 0/1] UBUNTU: SAUCE: Revert "crypto: api - Fix boot-up self-test race"

[Noah Wager]

BugLink: https://bugs.launchpad.net/bugs/2135716

SRU Justification:

[Impact]

Upstream stable updates applied the v6.12.13 commit "crypto: api - Fix boot-up self-test race" to noble 6.8. When crypto selftests are enabled (i.e. CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n) the system freezes during boot for 60 seconds and fails the selftest with a kernel error. This issue has also been observed upstream for 6.6, which caused the patch to be removed from stable updates for 6.6 [1]. Kernels 6.12+ work fine.

This was reproduced on a noble desktop VM and an NVIDIA Jetson AGX Orin, and the AGX error is shown below.

[ 70.635664] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 70.643757] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.643762] ------------[ cut here ]------------
[ 70.656053] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.656129] WARNING: CPU: 1 PID: 139 at crypto/testmgr.c:5900 alg_test+0x580/0x620
[ 70.656197] Modules linked in:
[ 70.656214] CPU: 1 PID: 139 Comm: cryptomgr_test Not tainted 6.8.12+ #22
[ 70.656223] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 00.0.0-dev-main_e11e99_3bea0 09/22/2025
[ 70.656228] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 70.656238] pc : alg_test+0x580/0x620
[ 70.656240] lr : alg_test+0x580/0x620
[ 70.656244] sp : ffff8000818f3d50
[ 70.656247] x29: ffff8000818f3d50 x28: 0000000000000000 x27: 0000000000000000
[ 70.656253] x26: 00000000ffffff92 x25: 00000000ffffffff x24: 0000000000000154
[ 70.656258] x23: ffffbbfb9e52e350 x22: 000000000000000e x21: ffff000086c83680
[ 70.656263] x20: ffff000086c83600 x19: ffffbbfb9c79dae8 x18: 00000000fffffffe
[ 70.656268] x17: 312d3d6372282064 x16: 656c696166206e6f x15: ffff8000818f3960
[ 70.656274] x14: 0000000000000000 x13: ffffbbfb9e4f2b5f x12: 00000000000001da
[ 70.656280] x11: 00000000ffffffea x10: ffffbbfb9dfa3e80 x9 : 0000000000000001
[ 70.656284] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : c0000000ffffefff
[ 70.656290] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : 0000000000000000
[ 70.656295] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00008101ddc0
[ 70.656302] Call trace:
[ 70.656308] alg_test+0x580/0x620
[ 70.656311] cryptomgr_test+0x24/0x44
[ 70.656322] kthread+0x110/0x114
[ 70.656338] ret_from_fork+0x10/0x20
[ 70.656358] ---[ end trace 0000000000000000 ]---
[ 132.075677] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 132.083791] alg: self-tests for sha224 using sha224-arm64 failed (rc=-110)

[Fix]

Revert commit "crypto: api - Fix boot-up self-test race".

[Test Plan]

To reproduce the issue:
1. Compile the stock noble generic kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
2. Boot the kernel on any platform, like a VM.
3. Observe boot stall.

To test the fix:
1. Revert commit in noble generic kernel.
2. Compile the modified kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
3. Boot the kernel on any platform, like a VM.
4. Boot should succeed with no delays or errors.

[Where problems could occur]

The regression potential is low, since this commit was dropped from stable 6.6 and the issue it aims to fix was never observed (it is only a theoretical problem). Therefore, 6.8 behavior should remain unchanged.

That said, the theoretical issue will be present after reverting this commit, which is a problem that could occur.

[1] https://lists-ec2.96boards.org/archives/list/lkft-triage@lists.linaro.org/message/2T73AZRFODFX57XXVWF6UD22CK6RFA44/

Noah Wager (1):
  UBUNTU: SAUCE: Revert "crypto: api - Fix boot-up self-test race"

 crypto/algapi.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.43.0