| 2019-10-17 12:09:19 |
bugproxy |
bug |
|
|
added bug |
| 2019-10-17 12:09:22 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 |
|
| 2019-10-17 12:09:23 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2019-10-17 12:09:26 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2019-10-17 12:30:35 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2019-10-17 12:30:41 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2019-10-17 12:30:46 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2019-10-17 12:31:21 |
Frank Heimes |
summary |
Change Config Option "CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y" -> "n" |
Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE from yes to no |
|
| 2019-10-17 18:43:02 |
Frank Heimes |
summary |
Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE from yes to no |
Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no |
|
| 2019-10-18 07:08:58 |
Frank Heimes |
description |
The Ubuntu kernel configuration contains CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y for s390.
This causes all standby memory configured for an LPAR to be used at IPL time.
Note that this is definetaly not what a user wants on s390.
The normal process is: define a certain amount of "base" memory which the system should use when IPL'ed, and define also a certain amount of "standby" memory which can be (also only partially) be additionaly used when necessary.
Also note that it is *not* possible to add additional memory to a runnung system, besides the amount of memory specified as "standby".
Therefore please change the kernel config option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE to "n" for s390. |
SRU Justification:
==================
[Impact]
* By default all standby memory that is configured to an LPAR is used at boot (IPL) time.
* But the standby memory is meant to be added and used on demand later (after IPL).
[Fix]
* 0001-Ubuntu-Config-Disabled-CONFIG_MEMORY_HOTPLUG_DEFAULT.patch
[Test Case]
* Configure an LPAR in it's Activation Profile with a certain amount of 'Initial' memory and some 'Reserved' memory on top.
* Re-activate the LPAR to make the changes take effect and boot (IPL) Ubuntu.
* Check with the help of free whether the reported memory is only the initial memory (actual) or initial+reserved (desired).
[Regression Potential]
* There is a certain regression potential, since some systems may have Initial and Reserved memory already defined today and have it already all in use under Linux (today obviously w/o having it dynamically added).
* If such a system got re-activated and rebooted, the memory size will then be what's defined as Initial memory and no longer Initial+Reserved.
* To be able to use the same size of the memory than before, the Reserved memory need to be either dynamically be added or the Initial memory re-configured to the sum of former Initial+Reserved.
* The latter case requires a re-activation of the LPAR, but since this corner case only happens after a reboot, a downtime is already in place for the re-activation.
* But overall the regression potential is low since it's for s390x only and the 'Reserved' memory option in the Activation Profile is rarely used.
[Other Info]
* In the past this config option was diabled for ppc64el, too.
__________
The Ubuntu kernel configuration contains CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y for s390.
This causes all standby memory configured for an LPAR to be used at IPL time.
Note that this is definetaly not what a user wants on s390.
The normal process is: define a certain amount of "base" memory which the system should use when IPL'ed, and define also a certain amount of "standby" memory which can be (also only partially) be additionaly used when necessary.
Also note that it is *not* possible to add additional memory to a runnung system, besides the amount of memory specified as "standby".
Therefore please change the kernel config option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE to "n" for s390. |
|
| 2019-10-18 07:09:03 |
Frank Heimes |
linux (Ubuntu): status |
New |
In Progress |
|
| 2019-10-18 07:09:09 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2019-10-18 07:09:13 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Frank Heimes (frank-heimes) |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
nominated for series |
|
Ubuntu Disco |
|
| 2019-10-18 08:19:02 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2019-10-18 08:19:30 |
Stefan Bader |
linux (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2019-10-18 08:19:32 |
Stefan Bader |
linux (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-10-18 08:19:36 |
Stefan Bader |
linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-10-21 03:31:03 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-10-21 03:31:09 |
Khaled El Mously |
linux (Ubuntu Disco): status |
New |
Fix Committed |
|
| 2019-10-21 03:31:15 |
Khaled El Mously |
linux (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2019-10-21 05:13:28 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2019-10-22 15:02:28 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-needed-disco |
|
| 2019-10-22 15:47:50 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-needed-disco |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-disco |
|
| 2019-10-22 20:27:20 |
Seth Forshee |
linux (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2019-10-23 10:21:03 |
Frank Heimes |
attachment added |
|
bionic_verification.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848492/+attachment/5299445/+files/bionic_verification.txt |
|
| 2019-10-23 10:21:29 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-disco |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-needed-disco |
|
| 2019-10-23 11:49:14 |
Frank Heimes |
attachment added |
|
disco_verification.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+attachment/5299466/+files/disco_verification.txt |
|
| 2019-10-23 11:49:38 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-needed-disco |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-done-disco |
|
| 2019-10-24 16:03:06 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-done-disco |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-done-disco verification-needed-eoan |
|
| 2019-10-24 16:53:54 |
Frank Heimes |
attachment added |
|
eoan_verification.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848492/+attachment/5299833/+files/eoan_verification.txt |
|
| 2019-10-24 16:54:24 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-done-disco verification-needed-eoan |
architecture-s39064 bugnameltc-181933 severity-high targetmilestone-inin1804 verification-done-bionic verification-done-disco verification-done-eoan |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2018-12207 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-0154 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-0155 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-11135 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-15793 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-17666 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-15098 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-17052 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-17053 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-17054 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-17055 |
|
| 2019-11-12 22:21:40 |
Launchpad Janitor |
cve linked |
|
2019-17056 |
|
| 2019-11-12 22:24:59 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-12-06 15:57:44 |
Launchpad Janitor |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2019-12-06 15:57:44 |
Launchpad Janitor |
cve linked |
|
2019-15794 |
|
| 2019-12-06 16:29:00 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
