From: "Diederik de Haas" <diederik@cknow-tech.com>
To: <linux-crypto@vger.kernel.org>
Subject: ERROR: alg: shash: ghash-neon test failed (wrong result) on test vector 1, cfg="init+update+final aligned buffer"
Date: Tue, 09 Dec 2025 20:36:32 +0100 [thread overview]
Message-ID: <DETXT7QI62KE.F3CGH2VWX1SC@cknow-tech.com> (raw)
Hi,
With either 6.18-rc1 or -rc2 I saw the above error in dmesg:
https://paste.sr.ht/~diederik/54ed00a4cdcf5f9285674cf940d53a1ffd7ecc4f
and then the stack trace in the dmesg warnings.
This was on a (Rockchip based) PineTab2 (rk3566) on arm64.
Didn't have time to report it then and then it seems like the error was
gone with 6.18-rc5, so I assumed it was fixed*.
Then I started up an Raspberry Pi 3B+ (also arm64) with Debian's 6.17.9
kernel ... and I saw that error again. I also tried Debian's 6.17.2 and
my own 6.18(.0) kernel and they also showed that error.
So I guess there is an actual problem?
For completeness, the error and warnings (incl stack trace) on 6.17.9:
```
[ 21.438404] alg: shash: ghash-neon test failed (wrong result) on test vector 1, cfg="init+update+final aligned buffer"
[ 21.448906] alg: self-tests for ghash using ghash-neon failed (rc=-22)
[ 21.448927] ------------[ cut here ]------------
[ 21.460059] alg: self-tests for ghash using ghash-neon failed (rc=-22)
[ 21.460231] WARNING: CPU: 0 PID: 650 at crypto/testmgr.c:5827 alg_test+0x92c/0x950
[ 21.474266] Modules linked in: ghash_ce gf128mul gcm ccm algif_aead des_generic libdes rfcomm algif_skcipher bnep aes_neon_blk md4 algif_hash af_alg evdev vc4 snd_soc_hdmi_codec brcmfmac_wcc snd_soc_core btsdio nls_ascii snd_compress brcmfmac microchip nls_cp437 bcm2835_v4l2(C) snd_pcm_dmaengine drm_exec brcmutil hci_uart bcm2835_mmal_vchiq(C) drm_display_helper vfat btqca fat videobuf2_vmalloc lan78xx btrtl cfg80211 videobuf2_memops cec videobuf2_v4l2 phylink btintel rc_core of_mdio btbcm videodev drm_client_lib fixed_phy fwnode_mdio drm_dma_helper snd_bcm2835(C) libphy videobuf2_common snd_pcm bluetooth mdio_bus mc drm_kms_helper snd_timer snd cpufreq_dt soundcore ecdh_generic rfkill raspberrypi_cpufreq pwrseq_core ledtrig_default_on bcm2835_thermal vchiq(C) pwm_bcm2835 bcm2835_rng leds_gpio pkcs8_key_parser drm efi_pstore configfs nfnetlink autofs4 ext4 crc16 mbcache jbd2 crc32c_cryptoapi onboard_usb_dev dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci bcm2835_wdt usb_common bcm2835 phy_generic i2c_bcm2835
[ 21.565523] CPU: 0 UID: 0 PID: 650 Comm: cryptomgr_test Tainted: G C 6.17.9+deb14-arm64 #1 PREEMPTLAZY Debian 6.17.9-1
[ 21.577700] Tainted: [C]=CRAP
[ 21.580655] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
[ 21.587014] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 21.594062] pc : alg_test+0x92c/0x950
[ 21.597746] lr : alg_test+0x92c/0x950
[ 21.601446] sp : ffff800081413d20
[ 21.604793] x29: ffff800081413dd0 x28: 0000000000000111 x27: 00000000ffffffea
[ 21.612030] x26: 0000000000000088 x25: ffffb3112dfa7d48 x24: 00000000ffffffff
[ 21.621241] x23: 0000000000000089 x22: 000000000104000e x21: ffff000006320e00
[ 21.629874] x20: ffffb3112f6d0000 x19: ffffb3112dfa9f48 x18: 0000000000000000
[ 21.638500] x17: 726f746365762074 x16: ffffb3112d52c1a8 x15: ffffb3112f1b45e0
[ 21.647115] x14: ffffb3112f0d7480 x13: 00000000000000c0 x12: 00000004ff201560
[ 21.655729] x11: 00000000000000c0 x10: 0000000000000d40 x9 : ffffb3112cf28078
[ 21.664327] x8 : ffff00000575dda0 x7 : 0000000000000004 x6 : 0000000000000000
[ 21.672936] x5 : 0000000000000000 x4 : ffff00000575d000 x3 : ffff000004ad2800
[ 21.681520] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00000575d000
[ 21.690116] Call trace:
[ 21.693925] alg_test+0x92c/0x950 (P)
[ 21.698952] cryptomgr_test+0x2c/0x58
[ 21.703972] kthread+0x148/0x240
[ 21.708535] ret_from_fork+0x10/0x20
[ 21.713440] ---[ end trace 0000000000000000 ]---
```
Hopefully this'll tell you where the (likely) problem is at.
Cheers,
Diederik
*) Reading my own comment from that paste ... I possibly switched to an
'rkbin' based U-Boot and that's why I didn't see it anymore
next reply other threads:[~2025-12-09 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 19:36 Diederik de Haas [this message]
2025-12-09 22:34 ` [PATCH] crypto: arm64/ghash - Fix incorrect output from ghash-neon Eric Biggers
2025-12-09 23:24 ` Herbert Xu
2025-12-10 0:30 ` Eric Biggers
2025-12-10 9:22 ` Diederik de Haas
2025-12-10 9:31 ` Ard Biesheuvel
2025-12-12 5:40 ` Eric Biggers
2025-12-15 7:54 ` Ard Biesheuvel
2025-12-15 20:16 ` Eric Biggers
2025-12-16 8:15 ` Ard Biesheuvel
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=DETXT7QI62KE.F3CGH2VWX1SC@cknow-tech.com \
--to=diederik@cknow-tech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.