| 2021-12-06 11:29:38 |
bugproxy |
bug |
|
|
added bug |
| 2021-12-06 11:29:41 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-195467 severity-high targetmilestone-inin2004 |
|
| 2021-12-06 11:29:43 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2021-12-06 11:29:49 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2021-12-06 12:55:13 |
Frank Heimes |
affects |
linux (Ubuntu) |
qemu (Ubuntu) |
|
| 2021-12-06 12:55:37 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2021-12-06 12:59:00 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2021-12-06 12:59:14 |
Frank Heimes |
qemu (Ubuntu): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Canonical Server Team (canonical-server) |
|
| 2021-12-06 12:59:21 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2021-12-06 13:28:02 |
Christian Ehrhardt |
qemu (Ubuntu): status |
New |
Incomplete |
|
| 2021-12-06 16:09:31 |
bugproxy |
attachment added |
|
0001-s390-sclp-get-machine-once-during-read-scp-cpu-info https://bugs.launchpad.net/bugs/1953338/+attachment/5545751/+files/0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch |
|
| 2021-12-06 16:19:41 |
bugproxy |
attachment added |
|
0002-s390-sclp-rework-sclp-boundary-checks https://bugs.launchpad.net/bugs/1953338/+attachment/5545762/+files/0002-s390-sclp-rework-sclp-boundary-checks.patch |
|
| 2021-12-06 16:19:44 |
bugproxy |
attachment added |
|
0003-s390-sclp-read-sccb-from-mem-based-on-provided-length https://bugs.launchpad.net/bugs/1953338/+attachment/5545763/+files/0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch |
|
| 2021-12-06 16:19:46 |
bugproxy |
attachment added |
|
0004-s390-sclp-check-sccb-len-before-filling-in-data https://bugs.launchpad.net/bugs/1953338/+attachment/5545764/+files/0004-s390-sclp-check-sccb-len-before-filling-in-data.patch |
|
| 2021-12-06 16:19:48 |
bugproxy |
attachment added |
|
0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries https://bugs.launchpad.net/bugs/1953338/+attachment/5545765/+files/0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch |
|
| 2021-12-06 16:19:51 |
bugproxy |
attachment added |
|
0006-s390-sclp-add-extended-length-sccb-support-for-kvm-guest https://bugs.launchpad.net/bugs/1953338/+attachment/5545766/+files/0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch |
|
| 2021-12-06 16:19:54 |
bugproxy |
attachment added |
|
0007-s390-guest-support-for-diagnose-0x318 https://bugs.launchpad.net/bugs/1953338/+attachment/5545767/+files/0007-s390-guest-support-for-diagnose-0x318.patch |
|
| 2021-12-06 16:19:56 |
bugproxy |
attachment added |
|
0008-s390-kvm-fix-diag318-propagation-and-reset-functiona https://bugs.launchpad.net/bugs/1953338/+attachment/5545768/+files/0008-s390-kvm-fix-diag318-propagation-and-reset-functiona.patch |
|
| 2021-12-07 06:39:15 |
Frank Heimes |
qemu (Ubuntu): status |
Incomplete |
New |
|
| 2021-12-07 14:34:26 |
Christian Ehrhardt |
qemu (Ubuntu): status |
New |
Fix Released |
|
| 2021-12-07 14:34:36 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Focal |
|
| 2021-12-07 14:34:36 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Focal) |
|
| 2021-12-07 14:35:17 |
Christian Ehrhardt |
qemu (Ubuntu Focal): status |
New |
Triaged |
|
| 2022-01-13 14:07:30 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2022-01-13 15:35:55 |
Christian Ehrhardt |
qemu (Ubuntu Focal): status |
Triaged |
Incomplete |
|
| 2022-01-21 03:59:53 |
bugproxy |
attachment added |
|
0001-s390-sclp-get-machine-once-during-read-scp-cpu-info https://bugs.launchpad.net/bugs/1953338/+attachment/5556015/+files/0001-s390-sclp-get-machine-once-during-read-scp-cpu-info.patch |
|
| 2022-01-21 03:59:54 |
bugproxy |
attachment added |
|
0002-s390-sclp-rework-sclp-boundary-checks https://bugs.launchpad.net/bugs/1953338/+attachment/5556016/+files/0002-s390-sclp-rework-sclp-boundary-checks.patch |
|
| 2022-01-21 03:59:56 |
bugproxy |
attachment added |
|
0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt https://bugs.launchpad.net/bugs/1953338/+attachment/5556017/+files/0003-s390-sclp-read-sccb-from-mem-based-on-provided-lengt.patch |
|
| 2022-01-21 03:59:58 |
bugproxy |
attachment added |
|
0004-s390-sclp-check-sccb-len-before-filling-in-data https://bugs.launchpad.net/bugs/1953338/+attachment/5556018/+files/0004-s390-sclp-check-sccb-len-before-filling-in-data.patch |
|
| 2022-01-21 04:10:03 |
bugproxy |
attachment added |
|
0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries https://bugs.launchpad.net/bugs/1953338/+attachment/5556021/+files/0005-s390-sclp-use-cpu-offset-to-locate-cpu-entries.patch |
|
| 2022-01-21 04:10:05 |
bugproxy |
attachment added |
|
0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g https://bugs.launchpad.net/bugs/1953338/+attachment/5556022/+files/0006-s390-sclp-add-extended-length-sccb-support-for-kvm-g.patch |
|
| 2022-01-21 04:10:07 |
bugproxy |
attachment added |
|
0007-s390-guest-support-for-diagnose-0x318 https://bugs.launchpad.net/bugs/1953338/+attachment/5556023/+files/0007-s390-guest-support-for-diagnose-0x318.patch |
|
| 2022-01-21 04:10:10 |
bugproxy |
attachment added |
|
0008-s390x-pv-Remove-sclp-boundary-checks https://bugs.launchpad.net/bugs/1953338/+attachment/5556024/+files/0008-s390x-pv-Remove-sclp-boundary-checks.patch |
|
| 2022-01-21 04:10:12 |
bugproxy |
attachment added |
|
0009-s390x-pv-Fix-diag318-PV-fencing https://bugs.launchpad.net/bugs/1953338/+attachment/5556025/+files/0009-s390x-pv-Fix-diag318-PV-fencing.patch |
|
| 2022-01-25 15:47:13 |
Frank Heimes |
description |
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) |
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) |
|
| 2022-01-25 16:10:47 |
Christian Ehrhardt |
tags |
architecture-s39064 bugnameltc-195467 severity-high targetmilestone-inin2004 |
architecture-s39064 block-proposed bugnameltc-195467 severity-high targetmilestone-inin2004 |
|
| 2022-01-26 14:21:01 |
Christian Ehrhardt |
qemu (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2022-01-26 14:26:58 |
Christian Ehrhardt |
description |
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) |
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
* "[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) |
|
| 2022-01-26 14:31:47 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2022-02-01 18:33:47 |
Brian Murray |
tags |
architecture-s39064 block-proposed bugnameltc-195467 severity-high targetmilestone-inin2004 |
architecture-s39064 block-proposed block-proposed-focal bugnameltc-195467 severity-high targetmilestone-inin2004 |
|
| 2022-02-01 18:34:59 |
Brian Murray |
qemu (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-02-01 18:35:01 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-02-01 18:35:03 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2022-02-01 18:35:07 |
Brian Murray |
tags |
architecture-s39064 block-proposed block-proposed-focal bugnameltc-195467 severity-high targetmilestone-inin2004 |
architecture-s39064 block-proposed block-proposed-focal bugnameltc-195467 severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
|
| 2022-02-01 18:56:40 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2022-02-02 11:52:29 |
Frank Heimes |
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 |
|
| 2022-02-02 11:52:55 |
Frank Heimes |
tags |
architecture-s39064 block-proposed block-proposed-focal bugnameltc-195467 severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
architecture-s39064 block-proposed block-proposed-focal bugnameltc-195467 severity-high targetmilestone-inin2004 verification-done verification-done-focal |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
qemu (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
cve linked |
|
2021-20196 |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
cve linked |
|
2021-20203 |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
cve linked |
|
2021-3682 |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
cve linked |
|
2021-3748 |
|
| 2022-02-28 12:38:54 |
Launchpad Janitor |
cve linked |
|
2021-3930 |
|
| 2022-03-10 07:30:10 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
