| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <900b7ee9e96e38b0d3cc088f3c6040be0915464b.camel@gmail.com> Date: Sun, 06 Oct 2024 10:47:40 +0200 From: Klaus Kudielka <klaus.kudielka@...il.com> To: regressions@...ts.linux.dev Cc: linux-kernel@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au> Subject: Re: [REGRESSION] alg: ahash: Several tests fail during boot on Turris Omnia Some more experimental evidence on this. I just evaluated the "selftest" status in /proc/crypto after boot. I looked at three versions, each with 5 boots. - v6.12-rc1 - 37da5d0ffa7b (the culprit) - 96ad59552059 (the parent of the culprit) v6.12-rc1 ========= Boot # 1 2 3 4 5 -------------------------------------------------------- mv-hmac-sha256 unknown unknown unknown passed unknown mv-hmac-sha1 passed unknown unknown passed unknown mv-hmac-md5 passed passed passed passed unknown mv-sha256 unknown unknown passed passed passed mv-sha1 passed unknown passed passed unknown mv-md5 passed passed passed passed unknown mv-cbc-aes passed passed passed passed passed mv-ecb-aes passed passed passed passed passed mv-cbc-des3-ede passed passed passed passed passed mv-ecb-des3-ede passed passed passed passed passed mv-cbc-des passed passed passed passed passed mv-ecb-des passed passed passed passed passed crc32c-generic passed passed passed passed passed sha224-generic passed passed passed passed passed sha256-generic passed passed passed passed passed 37da5d0ffa7b (“crypto: api - Do not wait for tests during registration”) ======================================================================== Boot # 1 2 3 4 5 -------------------------------------------------------- mv-hmac-sha256 unknown unknown unknown unknown unknown mv-hmac-sha1 unknown unknown unknown passed unknown mv-hmac-md5 unknown unknown unknown passed unknown mv-sha256 passed passed unknown unknown unknown mv-sha1 unknown passed unknown passed passed mv-md5 unknown passed passed passed unknown mv-cbc-aes passed passed passed passed passed mv-ecb-aes passed passed passed passed passed mv-cbc-des3-ede passed passed passed passed passed mv-ecb-des3-ede passed passed passed passed passed mv-cbc-des passed passed passed passed passed mv-ecb-des passed passed passed passed passed crc32c-generic passed passed passed passed passed sha224-generic passed passed passed passed passed sha256-generic passed passed passed passed passed 96ad59552059 (“crypto: api - Remove instance larval fulfilment”) ================================================================ Boot # 1 2 3 4 5 -------------------------------------------------------- mv-hmac-sha256 passed passed passed passed passed mv-hmac-sha1 passed passed passed passed passed mv-hmac-md5 passed passed passed passed passed mv-sha256 passed passed passed passed passed mv-sha1 passed passed passed passed passed mv-md5 passed passed passed passed passed mv-cbc-aes passed passed passed passed passed mv-ecb-aes passed passed passed passed passed mv-cbc-des3-ede passed passed passed passed passed mv-ecb-des3-ede passed passed passed passed passed mv-cbc-des passed passed passed passed passed mv-ecb-des passed passed passed passed passed crc32c-generic passed passed passed passed passed sha224-generic passed passed passed passed passed sha256-generic passed passed passed passed passed If I interprett regzbot history correctly, there was already one fix applied on top of the culprit. But e7a4142b35ce is already part of v6.12-rc1, and obviously did not solve my problem. Best regards, Klaus
Powered by blists - more mailing lists