------- Comment From janis.schoetterl-glau...@ibm.com 2022-02-24 04:54 EDT------- You only need the s390 specific lines for the two conflicts, i.e.
+/s390x/tprot and +#define KVM_CAP_S390_MEM_OP_EXTENSION 210 -- 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/1933179 Title: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. Value: Interoperability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+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
