Hello Thomas, thank you! Was also my impression that a backport is probably best. And the backport applies cleanly on jammy master-next (so yes, that is what we have to use for the next and upcoming kernel of an Ubuntu release).
Proceeding now with the kernel SRU ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2074380 Title: [UBUNTU 22.04] kernel: s390/cpum_cf: make crypto counters upward compatible Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: Description: kernel: s390/cpum_cf: make crypto counters upward compatible Symptom: The CPU Measurement facility crypto counter set is not listed in the device sysfs tree. Problem: The CPU Measurement facility crypto counter set is not exported in the sysfs directory /sys/devices/cpum_cf/events. The attribute files for each CPU-MF counter defined in the crypto counter set is missing. This is caused by the counter second version number of the CPU Measurement Facility hardware being incremented on new machines. This causes a sanity check to fail, but the counters are supported by hardware. Solution: Remove upper limit in counter second version number check. Reproduction: Run command on a new machine generation: # ls -l /sys/devices/cpum_cf/events/ | grep AES # If the output is empty than this patch is required. The output should be: # ls /sys/devices/cpum_cf/events/ | grep AES AES_BLOCKED_CYCLES AES_BLOCKED_FUNCTIONS AES_CYCLES AES_FUNCTIONS # Upstream-ID of fix: f10933cbd2dfddf6273698a45f76db9bafd8150f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2074380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
