An updated disco master-next tree now shows the following: $ git log --oneline | grep -m 1 "do nosimd fallback manually" ccfd9be crypto: vmx - ghash: do nosimd fallback manually $ git describe --tags --contains ccfd9be Ubuntu-5.0.0-26.27~34 $ git log --oneline | grep -m 1 "always increment IV as quadword" b5df7b3 crypto: vmx - CTR: always increment IV as quadword $ git describe --tags --contains b5df7b3 Ubuntu-5.0.0-26.27~394 $ git log --oneline | grep -m 1 "fix copy-paste error in CTR mode" 6cef65e crypto: vmx - fix copy-paste error in CTR mode $ git describe --tags --contains 6cef65e Ubuntu-5.0.0-24.25~116
That kernel "Ubuntu-5.0.0-26" incl. everything needed and 5.0.0.27 is in disco proposed: linux-generic | 5.0.0.27.28 | disco-proposed | s390x
Hence, would you mind re-trying with the latest disco-proposed kernel?
An updated disco master-next tree now shows the following: 5.0.0-26. 27~34 5.0.0-26. 27~394 5.0.0-24. 25~116
$ git log --oneline | grep -m 1 "do nosimd fallback manually"
ccfd9be crypto: vmx - ghash: do nosimd fallback manually
$ git describe --tags --contains ccfd9be
Ubuntu-
$ git log --oneline | grep -m 1 "always increment IV as quadword"
b5df7b3 crypto: vmx - CTR: always increment IV as quadword
$ git describe --tags --contains b5df7b3
Ubuntu-
$ git log --oneline | grep -m 1 "fix copy-paste error in CTR mode"
6cef65e crypto: vmx - fix copy-paste error in CTR mode
$ git describe --tags --contains 6cef65e
Ubuntu-
That kernel "Ubuntu-5.0.0-26" incl. everything needed and 5.0.0.27 is in disco proposed:
linux-generic | 5.0.0.27.28 | disco-proposed | s390x
Hence, would you mind re-trying with the latest disco-proposed kernel?