[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
This bug was fixed in the package qemu - 1:4.2-3ubuntu6.21 --- qemu (1:4.2-3ubuntu6.21) focal-security; urgency=medium * SECURITY UPDATE: crash or code exec in USB redirector device emulation - debian/patches/CVE-2021-3682.patch: fix free call in hw/usb/redirect.c. - CVE-2021-3682 * SECURITY UPDATE: heap use-after-free in virtio_net_receive_rcu - debian/patches/CVE-2021-3748.patch: fix use after unmap/free for sg in hw/net/virtio-net.c. - CVE-2021-3748 * SECURITY UPDATE: off-by-one error in mode_sense_page() - debian/patches/CVE-2021-3930.patch: MODE_PAGE_ALLS not allowed in MODE SELECT commands in hw/scsi/scsi-disk.c. - CVE-2021-3930 * SECURITY UPDATE: NULL dereference in floppy disk emulator - debian/patches/CVE-2021-20196-1.patch: Extract blk_create_empty_drive() in hw/block/fdc.c. - debian/patches/CVE-2021-20196-2.patch: kludge missing floppy drive in hw/block/fdc.c. - CVE-2021-20196 * SECURITY UPDATE: integer overflow in vmxnet3 NIC emulator - debian/patches/CVE-2021-20203.patch: validate configuration values during activate in hw/net/vmxnet3.c. - CVE-2021-20203 -- Marc Deslauriers Tue, 22 Feb 2022 12:44:44 -0500 ** Changed in: qemu (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20203 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3682 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3748 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3930 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
There was an issue with our builders yesterday, restarting the same build today worked again - package is now there (at the PPA). I did a quick test (since I had the env. still from the LP#1953334 verification. And from what I understood it seems to be fine:$ sudo grep "cpnc to 4" /sys/kernel/debug/s390dbf/kvm-1479/sprintf 00 01643802097:936371 3 - 10 00013fa231c4 00[20018000-31852d02]: setting cpnc to 4 ** Attachment added: "qemu_PPA_test_on_focal.txt" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953338/+attachment/5558743/+files/qemu_PPA_test_on_focal.txt ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
The block-proposed tags are release specific so I've added block- proposed-focal. ** Tags added: block-proposed-focal ** Changed in: qemu (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Description changed: SRU Justification: == [Impact] * Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. * A fix is needed to enhance problem determination of guest kernel under KVM using DIAG 0x318 instruction execution. * The s390x diagnose 318 instruction sets the control program name code (CPNC) and control program version code (CPVC) to provide useful information regarding the OS during debugging. * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment. + * The user story to this is, that s390x clearly is a platform that has + virtualization for ages, and as part of that established diag calls to + allow you add data to guests. This helps live management and/or guest + debugging in case of problems. For KVM guests this data is + wrong/incomplete so far and this is the fix for it. + You might want to see [1] for the base-feature that this fixes. And do + not say it is ugly, I did not send the PoP page about diags :-) + + [1]: https://git.mentality.rip/OpenE2K/qemu-e2k/commit/fabdada9357b + [Fix] * In general the following 9 patches (backports) are needed: * "[PATCH 1/9] s390/sclp: get machine once during read scp/cpu info" - https://launchpadlibrarian.net/581388471/0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch + https://launchpadlibrarian.net/581388471/0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch * "[PATCH 2/9] s390/sclp: rework sclp boundary checks" - https://launchpadlibrarian.net/581388472/0002-s390-sclp-rework-sclp-boundary-checks.patch + https://launchpadlibrarian.net/581388472/0002-s390-sclp-rework-sclp-boundary-checks.patch * "[PATCH 3/9] s390/sclp: read sccb from mem based on provided length" - https://launchpadlibrarian.net/581388474/0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch + https://launchpadlibrarian.net/581388474/0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch * "[PATCH 4/9] s390/sclp: check sccb len before filling in data" - https://launchpadlibrarian.net/581388476/0004-s390-sclp-check-sccb-len-before-filling-in-data.patch + https://launchpadlibrarian.net/581388476/0004-s390-sclp-check-sccb-len-before-filling-in-data.patch * "[PATCH 5/9] s390/sclp: use cpu offset to locate cpu entries" - https://launchpadlibrarian.net/581389965/0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch + https://launchpadlibrarian.net/581389965/0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch * "[PATCH 6/9] s390/sclp: add extended-length sccb support for kvm guest" - https://launchpadlibrarian.net/581389970/0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch + https://launchpadlibrarian.net/581389970/0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch * "[PATCH 7/9] s390: guest support for diagnose 0x318" - https://launchpadlibrarian.net/581389974/0007-s390-guest-support-for-diagnose-0x318.patch + https://launchpadlibrarian.net/581389974/0007-s390-guest-support-for-diagnose-0x318.patch * "[PATCH 8/9] s390x: pv: Remove sclp boundary checks" - https://launchpadlibrarian.net/581389981/0008-s390x-pv-Remove-sclp-boundary-checks.patch + https://launchpadlibrarian.net/581389981/0008-s390x-pv-Remove-sclp-boundary-checks.patch * "[PATCH 9/9] s390x: pv: Fix diag318 PV fencing" - https://launchpadlibrarian.net/581389982/0009-s390x-pv-Fix-diag318-PV-fencing.patch - + https://launchpadlibrarian.net/581389982/0009-s390x-pv-Fix-diag318-PV-fencing.patch + [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host. * And setup an Ubuntu KVM virtual machine on top. * It can then be observed if the CPNC (diag318 data) has been successfully set by looking at the s390dbf messages for the KVM guest. * The CPNC will always be 4 (denotes Linux environment). * Another way to test this is by running the sync_regs_test under tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the kernel self test suite can trigger this. * It is important that the patched qemu is tested with correct patched kernel, since one required the other - they can be found here: - qemu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4767 - kernel: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334 + qemu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4767 + kernel: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334 [Where problems could occur] * The approach here is to provide additional debug and diagnose information on top. * Hence even if the diag318 changes are broken, the existing functionality shouldn't be harmed. - * However, with the functional changes broken code could be introduced (e.g. due to erroneous pointer arithmetic for example) that does not compile or causes crashes. But this is
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: qemu (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Uploaded to focal-unapproved ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Description changed: + SRU Justification: + == + + [Impact] + + * Hardware diagnose data (diag 318) of KVM guest kernel cannot be + handled. + + * A fix is needed to enhance problem determination of guest kernel under + KVM using DIAG 0x318 instruction execution. + + * The s390x diagnose 318 instruction sets the control program name code + (CPNC) and control program version code (CPVC) to provide useful + information regarding the OS during debugging. + + * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment. + + [Fix] + + * In general the following 9 patches (backports) are needed: + + * "[PATCH 1/9] s390/sclp: get machine once during read scp/cpu info" + https://launchpadlibrarian.net/581388471/0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch + + * "[PATCH 2/9] s390/sclp: rework sclp boundary checks" + https://launchpadlibrarian.net/581388472/0002-s390-sclp-rework-sclp-boundary-checks.patch + + * "[PATCH 3/9] s390/sclp: read sccb from mem based on provided length" + https://launchpadlibrarian.net/581388474/0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch + + * "[PATCH 4/9] s390/sclp: check sccb len before filling in data" + https://launchpadlibrarian.net/581388476/0004-s390-sclp-check-sccb-len-before-filling-in-data.patch + + * "[PATCH 5/9] s390/sclp: use cpu offset to locate cpu entries" + https://launchpadlibrarian.net/581389965/0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch + + * "[PATCH 6/9] s390/sclp: add extended-length sccb support for kvm guest" + https://launchpadlibrarian.net/581389970/0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch + + * "[PATCH 7/9] s390: guest support for diagnose 0x318" + https://launchpadlibrarian.net/581389974/0007-s390-guest-support-for-diagnose-0x318.patch + + * "[PATCH 8/9] s390x: pv: Remove sclp boundary checks" + https://launchpadlibrarian.net/581389981/0008-s390x-pv-Remove-sclp-boundary-checks.patch + + * "[PATCH 9/9] s390x: pv: Fix diag318 PV fencing" + https://launchpadlibrarian.net/581389982/0009-s390x-pv-Fix-diag318-PV-fencing.patch + + [Test Case] + + * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host. + + * And setup an Ubuntu KVM virtual machine on top. + + * It can then be observed if the CPNC (diag318 data) has been + successfully set by looking at the s390dbf messages for the KVM guest. + + * The CPNC will always be 4 (denotes Linux environment). + + * Another way to test this is by running the sync_regs_test under + tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the + kernel self test suite can trigger this. + + * It is important that the patched qemu is tested with correct patched kernel, since one required the other - they can be found here: + qemu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4767 + kernel: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334 + + [Where problems could occur] + + * The approach here is to provide additional debug and diagnose + information on top. + + * Hence even if the diag318 changes are broken, the existing + functionality shouldn't be harmed. + + * However, with the functional changes broken code could be introduced (e.g. due to erroneous pointer arithmetic for example) that does not compile or causes crashes. But this is what the test builds are for + qemu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4767 + (kernel: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334) + + * On top the diag318 diagnose data might not properly provided - maybe + empty or wrong. Again that is what the test builds and the verification + later is targeted at. + + [Other] + + * LP#1953334 is related to this bug and covers the Kernel part. + __ + Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM Solution provided by Collin: All patches are provided to enable the DIAGNOSE 0x318 problem determination aid for a QEMU guest. Analogous KVM patches are required. This solution required the prerequisite Extended-Length SCCB patches as well. I've applied a bugfix related to resetting the diag318 to one of the patches (one line fix -- upstream conversation here: https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg03618.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
FYI - right now I have nothing else in the SRU queue for qemu. The plan to handle this upload without being a "useless" download for any non-s390x users will be that we drive the SRU normally but set block-proposed. There it will be picked up by a subsequent qemu security update in not too much time. @fheimes - could you add your SRU template content for this case here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Thank you for the backported patches, With those I've created a test PPA for Focal at [1] (still building atm). @Frank AFAIK you need that to test the current proposed kernel. Once you can confirm me that this looks good we can prep and kick off the SRU process of this upload here as well. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4767 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Incomplete since we wait for the proper rebase for the backports as I asked in early December. ** Changed in: qemu (Ubuntu Focal) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Note: this is related to bug https://bugs.launchpad.net/bugs/1953334 It shares the motivation and the test steps. Both fixes can exists along (no hard version requirement needed in he uploads) but only when both are together it can fully work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
They might be backported to plain 4.2, but they do not apply cleanly to 1:4.2-3ubuntu6.19. 0001 & 0002: The patch directly from upstream git applies, but your backport does not - so I just used cherry picks 0003: Neither your backprt nor a cherry pick worked as-is. Here things start to be rather different and instead of bad-backporting - and potentially even missing the point what the target was - I think i use this opportunity to ask. 1. What was this meant for - Focal? 2. For a backport to exactly what Focal has right see below: I guess you do not want to think about Debian packaging too much, you can do so via (there are many ways, but this is at least one): git clone -b ubuntu/focal-devel https://git.launchpad.net/ubuntu/+source/qemu cd qemu QUILT_PATCHES="debian/patches" quilt push --fuzz=0 -a git add . git commit -m "Current Focal base" This will be 4.2 + all patches in Ubuntu for you to work with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Thanks for the provided backports. So far I was assuming this is a new feat for Jammy, but now no more. Maybe we need to talk about what the target of this bug is - is it Focal and therefore the backport target here was 4.2 :-) backport/origin upstream-hash patch B 912d70d2 0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch B db13387c 0002-s390-sclp-rework-sclp-boundary-checks.patch B c1db53a5 0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch O 0260b978 0004-s390-sclp-check-sccb-len-before-filling-in-data.patch O 1a7a5688 0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch B 1ecd6078 0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch B fabdada9 0007-s390-guest-support-for-diagnose-0x318.patch O e2c6cd56 0008-s390-kvm-fix-diag318-propagation-and-reset-functiona.patch Of these 1,2,3,6,7 are in qemu 5.2 already. 4,5 were part of the same PR and also in 5.2, just didn't need backporting Finally patch 8 came in a later PR, but still is part of 5.2. Therefore I set this to fix released, but add a Focal task assuming (please confirm) that you wanted to target that. ** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Also affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
I've made some patched test kernel available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
Thanks for the heads up, Please let us know when the upstream discussion settled and there is a commit id we shall import. Furthermore as usual if this shall go to older active releases I wanted to ask from your dev/testing what the best way to trigger/fake diag 318 for testing would be? ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953338] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part
** Package changed: linux (Ubuntu) => qemu (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: qemu (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Server Team (canonical-server) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953338 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
