While preparing an update to 3.0.13 for Noble, I started encoutering testsuite failures.
The cause is the AES patch combined with 3.0.13 (more specifically with the dupctx patches. The problematic combination looks something like the following:
- AES-GCM-enabled-with-AVX512-vAES-and-vPCLMULQDQ
- make-inability-to-dup-clone-ciphers-an-error
- Add-dupctx-support-to-aead-ciphers
- Fix-a-key-repointing-in-various-ciphers (this is probably only needed to avoid merge conflicts and not a cause of the issue)
This happens both on Intel and AMD systems which have the corresponding CPU features.
I am going to prepare 3.0.13 _without_ the AES patch from here and I will continue to investigate this with upstream's 3.2 (since this is a rare CPU feature, it's possible CI tests don't exercise it).
While preparing an update to 3.0.13 for Noble, I started encoutering testsuite failures.
The cause is the AES patch combined with 3.0.13 (more specifically with the dupctx patches. The problematic combination looks something like the following: enabled- with-AVX512- vAES-and- vPCLMULQDQ to-dup- clone-ciphers- an-error support- to-aead- ciphers repointing- in-various- ciphers (this is probably only needed to avoid merge conflicts and not a cause of the issue)
- AES-GCM-
- make-inability-
- Add-dupctx-
- Fix-a-key-
This happens both on Intel and AMD systems which have the corresponding CPU features.
I am going to prepare 3.0.13 _without_ the AES patch from here and I will continue to investigate this with upstream's 3.2 (since this is a rare CPU feature, it's possible CI tests don't exercise it).