| 2017-12-07 13:37:12 |
Thadeu Lima de Souza Cascardo |
bug |
|
|
added bug |
| 2017-12-07 13:37:37 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Trusty |
|
| 2017-12-07 13:37:37 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Bionic |
|
| 2017-12-07 13:37:37 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-12-07 13:37:37 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Artful |
|
| 2017-12-07 13:37:37 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-12-07 13:55:22 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu): status |
New |
In Progress |
|
| 2017-12-07 13:55:35 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu): importance |
Undecided |
High |
|
| 2017-12-07 13:55:38 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu): assignee |
|
Thadeu Lima de Souza Cascardo (cascardo) |
|
| 2017-12-07 14:37:16 |
Thadeu Lima de Souza Cascardo |
bug task added |
|
linux (Ubuntu) |
|
| 2017-12-07 14:37:25 |
Thadeu Lima de Souza Cascardo |
bug task deleted |
makedumpfile (Ubuntu) |
|
|
| 2017-12-07 14:37:31 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu): status |
New |
In Progress |
|
| 2017-12-07 14:37:34 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2017-12-07 14:37:37 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu): assignee |
|
Thadeu Lima de Souza Cascardo (cascardo) |
|
| 2017-12-07 17:35:57 |
Thadeu Lima de Souza Cascardo |
description |
When panic_timeout is set, the user would expect that the system would reboot after some timeout after a panic.
However, on powerpc architecture, a panic notifier may not ever return and even shutdown the system. The main example that impacts platforms we support is pseries calling RTAS ibm,os-term.
That panic notifier and calling RTAS ibm,os-term is useful for fadump, so this should not be impacted.
The Linux code has changed back and forth on considering the panic_timeout setting and checking whether ibm,extended-os-term was available. Unfortunately, recent changes on qemu led to the guest being shut down when calling ibm,os-term even when ibm,extended-os-term was available.
Luckily, upstream Linux already has the change that does not call ibm,os-term on panic, but only during fadump. So, we can use that commit for fixing this. Changing qemu itself is harder as: 1) qemu community already decided some qemu settings should override PAPR; 2) updating deployed hypervisor is harder than updating our guest kernels.
Cascardo. |
[Impact]
When panic_timeout is set, the user would expect the system to reboot. However, it is shutdown, possibly requiring user intervention to power on the system again. This may impact availability. This happens under certain versions of qemu (2.10+) emulating pseries.
[Test Case]
Built kernels (trusty, xenial, zesty, artful) have been tested and they reboot after the fix, when running under an affected qemu.
[Regression Potential]
fadump might require that RTAS ibm,os-term be called. The fix should still allow it to be called when fadump is registered.
-----------
When panic_timeout is set, the user would expect that the system would reboot after some timeout after a panic.
However, on powerpc architecture, a panic notifier may not ever return and even shutdown the system. The main example that impacts platforms we support is pseries calling RTAS ibm,os-term.
That panic notifier and calling RTAS ibm,os-term is useful for fadump, so this should not be impacted.
The Linux code has changed back and forth on considering the panic_timeout setting and checking whether ibm,extended-os-term was available. Unfortunately, recent changes on qemu led to the guest being shut down when calling ibm,os-term even when ibm,extended-os-term was available.
Luckily, upstream Linux already has the change that does not call ibm,os-term on panic, but only during fadump. So, we can use that commit for fixing this. Changing qemu itself is harder as: 1) qemu community already decided some qemu settings should override PAPR; 2) updating deployed hypervisor is harder than updating our guest kernels.
Cascardo. |
|
| 2018-01-23 10:03:24 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2018-01-23 10:03:32 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2018-01-23 10:03:44 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2018-01-23 10:03:58 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Trusty) |
|
| 2018-02-20 08:51:30 |
Stefan Bader |
linux (Ubuntu Artful): importance |
Undecided |
High |
|
| 2018-02-20 08:51:33 |
Stefan Bader |
linux (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2018-02-20 08:51:36 |
Stefan Bader |
linux (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2018-02-20 08:51:44 |
Stefan Bader |
linux (Ubuntu Artful): status |
New |
Fix Committed |
|
| 2018-02-20 09:14:12 |
Stefan Bader |
linux (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2018-02-20 09:14:17 |
Stefan Bader |
linux (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2018-02-23 15:46:36 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
In Progress |
Fix Released |
|
| 2018-03-19 10:55:01 |
Stefan Bader |
tags |
|
verification-needed-trusty |
|
| 2018-03-19 10:56:14 |
Stefan Bader |
tags |
verification-needed-trusty |
verification-needed-trusty verification-needed-xenial |
|
| 2018-03-19 10:58:27 |
Stefan Bader |
tags |
verification-needed-trusty verification-needed-xenial |
verification-needed-artful verification-needed-trusty verification-needed-xenial |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
linux (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-0861 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-1000407 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-15129 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-16994 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17448 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17450 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17741 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17805 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17806 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17807 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-1000026 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5332 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5333 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5344 |
|
| 2018-04-04 09:21:37 |
Launchpad Janitor |
linux (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2018-04-04 09:21:37 |
Launchpad Janitor |
cve linked |
|
2017-11089 |
|
| 2018-04-04 09:21:37 |
Launchpad Janitor |
cve linked |
|
2017-12762 |
|
| 2018-04-04 09:21:37 |
Launchpad Janitor |
cve linked |
|
2017-5715 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-16995 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-17862 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-5753 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2018-8043 |
|
