| 2019-01-18 13:29:51 |
bugproxy |
bug |
|
|
added bug |
| 2019-01-18 13:29:54 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-174838 severity-medium targetmilestone-inin1804 |
|
| 2019-01-18 13:29:55 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2019-01-18 13:30:00 |
bugproxy |
affects |
ubuntu |
qemu (Ubuntu) |
|
| 2019-01-20 13:15:18 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2019-01-20 13:15:30 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2019-01-20 13:15:34 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
Medium |
|
| 2019-01-20 13:16:12 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Christian Ehrhardt (paelzer) |
|
| 2019-01-22 08:25:23 |
Christian Ehrhardt |
tags |
architecture-s39064 bugnameltc-174838 severity-medium targetmilestone-inin1804 |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 |
|
| 2019-01-22 08:25:29 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-01-22 08:25:29 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Cosmic) |
|
| 2019-01-22 08:25:29 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-01-22 08:25:29 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Bionic) |
|
| 2019-01-22 08:42:12 |
Christian Ehrhardt |
qemu (Ubuntu): status |
New |
In Progress |
|
| 2019-01-22 08:45:07 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2019-01-22 09:29:22 |
bugproxy |
attachment added |
|
Diag 308 test case https://bugs.launchpad.net/bugs/1812384/+attachment/5231382/+files/diag308.elf |
|
| 2019-01-22 10:36:47 |
Christian Ehrhardt |
description |
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
[Impact]
* diag308 doesn't behave correctly (hw error instead of program
interrupt)
* Solution; Backport upstream accepted fix
[Test Case]
* Download the test image in comment #3
* Run the test kernel in qemu (on s390x) like:
/usr/local/bin/qemu-system-s390x -nodefaults -nographic -machine s390-ccw-virtio,accel=kvm -chardev stdio,id=con0 -device sclpconsole,chardev=con0 -kernel s390x/diag308.elf
* Should report a proper abort/exception like
ABORT: diag308: Unexpected program interrupt: 6 at 0x134be, ilen 4
Without the fix it is a hard crash
[Regression Potential]
* In both cases the guest breaks, with the fix in place it breaks with a
better message and the guest kernel could actually handle the program
interrupt if it wanted.
Since the old case was a full crash of the qemu userspace and this si
the only code path modified I can't see potential regressions triggered
by this change.
[Other Info]
* n/a
---
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
|
| 2019-01-22 10:38:06 |
Christian Ehrhardt |
description |
[Impact]
* diag308 doesn't behave correctly (hw error instead of program
interrupt)
* Solution; Backport upstream accepted fix
[Test Case]
* Download the test image in comment #3
* Run the test kernel in qemu (on s390x) like:
/usr/local/bin/qemu-system-s390x -nodefaults -nographic -machine s390-ccw-virtio,accel=kvm -chardev stdio,id=con0 -device sclpconsole,chardev=con0 -kernel s390x/diag308.elf
* Should report a proper abort/exception like
ABORT: diag308: Unexpected program interrupt: 6 at 0x134be, ilen 4
Without the fix it is a hard crash
[Regression Potential]
* In both cases the guest breaks, with the fix in place it breaks with a
better message and the guest kernel could actually handle the program
interrupt if it wanted.
Since the old case was a full crash of the qemu userspace and this si
the only code path modified I can't see potential regressions triggered
by this change.
[Other Info]
* n/a
---
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
[Impact]
* diag308 doesn't behave correctly (hw error instead of program
interrupt)
* Solution; Backport upstream accepted fix
[Test Case]
* Download the test image in comment #3
* Run the test kernel in qemu (on s390x) like:
/usr/local/bin/qemu-system-s390x -nodefaults -nographic -machine s390-ccw-virtio,accel=kvm -chardev stdio,id=con0 -device sclpconsole,chardev=con0 -kernel s390x/diag308.elf
* Should report a proper abort/exception like
ABORT: diag308: Unexpected program interrupt: 6 at 0x134be, ilen 4
Without the fix it is a hard crash
[Regression Potential]
* In both cases the guest breaks, with the fix in place it breaks with a
better message and the guest kernel could actually handle the program
interrupt if it wanted.
Since the old case was a full crash of the qemu userspace and this si
the only code path modified I can't see potential regressions triggered
by this change.
[Other Info]
* I doubt we call a special test kernel a "real case" for the SRU, but
future guests (e.g. Ubuntu 20.04) might trigger subcodes not yet
known to older qmeu (e.g. in 18.04) so adding this is a good safety
net for any such upcoming changes.
---
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
qemu (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2016-10028 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2017-8284 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2017-9060 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-10839 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-11806 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-12617 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-15746 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-16847 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-16867 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-16872 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-17958 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-17962 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-17963 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-18438 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-18849 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-18954 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-19364 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-19489 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-19665 |
|
| 2019-01-30 22:24:10 |
Launchpad Janitor |
cve linked |
|
2018-3639 |
|
| 2019-01-31 15:53:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/362539 |
|
| 2019-01-31 15:56:49 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/362540 |
|
| 2019-02-01 10:29:51 |
Christian Ehrhardt |
description |
[Impact]
* diag308 doesn't behave correctly (hw error instead of program
interrupt)
* Solution; Backport upstream accepted fix
[Test Case]
* Download the test image in comment #3
* Run the test kernel in qemu (on s390x) like:
/usr/local/bin/qemu-system-s390x -nodefaults -nographic -machine s390-ccw-virtio,accel=kvm -chardev stdio,id=con0 -device sclpconsole,chardev=con0 -kernel s390x/diag308.elf
* Should report a proper abort/exception like
ABORT: diag308: Unexpected program interrupt: 6 at 0x134be, ilen 4
Without the fix it is a hard crash
[Regression Potential]
* In both cases the guest breaks, with the fix in place it breaks with a
better message and the guest kernel could actually handle the program
interrupt if it wanted.
Since the old case was a full crash of the qemu userspace and this si
the only code path modified I can't see potential regressions triggered
by this change.
[Other Info]
* I doubt we call a special test kernel a "real case" for the SRU, but
future guests (e.g. Ubuntu 20.04) might trigger subcodes not yet
known to older qmeu (e.g. in 18.04) so adding this is a good safety
net for any such upcoming changes.
---
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
[Impact]
* diag308 doesn't behave correctly (hw error instead of program
interrupt)
* Solution; Backport upstream accepted fix
[Test Case]
* Download the test image in comment #3
* Run the test kernel in qemu (on s390x) like:
qemu-system-s390x -nodefaults -nographic -machine s390-ccw-virtio,accel=kvm -chardev stdio,id=con0 -device sclpconsole,chardev=con0 -kernel diag308.elf
* Should report a proper abort/exception like
ABORT: diag308: Unexpected program interrupt: 6 at 0x134be, ilen 4
Without the fix it is a hard crash
[Regression Potential]
* In both cases the guest breaks, with the fix in place it breaks with a
better message and the guest kernel could actually handle the program
interrupt if it wanted.
Since the old case was a full crash of the qemu userspace and this si
the only code path modified I can't see potential regressions triggered
by this change.
[Other Info]
* I doubt we call a special test kernel a "real case" for the SRU, but
future guests (e.g. Ubuntu 20.04) might trigger subcodes not yet
known to older qmeu (e.g. in 18.04) so adding this is a good safety
net for any such upcoming changes.
---
The presence of subcodes is indicated by checking some query subcode.
For example 6 will indicate that 3-6 are available. So future systems
might call new subcodes to check for new features. This should not
trigger a hw error, instead we return the architectured specification
exception.
Commit has been accepted by maintainer:
https://github.com/cohuck/qemu/commit/f0646afaccf6bc1b196fc068eef75938db303814
Commit ID will be provided once it's upstream: |
|
| 2019-02-01 12:26:35 |
Christian Ehrhardt |
qemu (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-01 12:26:36 |
Christian Ehrhardt |
qemu (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-05 10:08:17 |
Frank Heimes |
qemu (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-02-05 10:08:21 |
Frank Heimes |
qemu (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-02-05 19:29:22 |
Brian Murray |
qemu (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-02-05 19:29:25 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-02-05 19:29:27 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-02-05 19:29:31 |
Brian Murray |
tags |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-needed verification-needed-cosmic |
|
| 2019-02-06 11:56:34 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-needed verification-needed-cosmic |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-done verification-done-cosmic |
|
| 2019-02-14 16:23:53 |
Launchpad Janitor |
qemu (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-02-14 16:24:11 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-02-25 12:11:07 |
Łukasz Zemczak |
qemu (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-02-25 12:11:08 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-02-25 12:11:12 |
Łukasz Zemczak |
tags |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-done verification-done-cosmic |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-done-cosmic verification-needed verification-needed-bionic |
|
| 2019-02-25 12:34:59 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2019-02-25 13:01:44 |
Frank Heimes |
attachment added |
|
verification_bionic.txt https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1812384/+attachment/5241550/+files/verification_bionic.txt |
|
| 2019-02-25 13:02:21 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-done-cosmic verification-needed verification-needed-bionic |
architecture-s39064 bugnameltc-174838 qemu-19.04 severity-medium targetmilestone-inin1804 verification-done verification-done-bionic verification-done-cosmic |
|
| 2019-03-04 16:41:31 |
Launchpad Janitor |
qemu (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-03-04 16:51:47 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
