memory-hotplug test needs to be fixed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Xenial |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Zesty |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Artful |
Fix Released
|
Undecided
|
Po-Hsu Lin |
Bug Description
SRU Justification:
Impact:
The memory-hotplug test in the kernel tree (tools/
1. The test will pass even the memory blocks are failed to be offlined [1].
2. It's using a random number generator to decide if each memory block needs to be offlined, which is not ideal for testing as the block it tries to unplug might be different between two runs.
3. The "-r" flag, percent-
Fix:
Apply the following patch from upstream can fix these issues:
593f9278 - selftests: typo correction for memory-hotplug test
a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test
72441ea5 - selftests: check percentage range for memory-hotplug test
02d8f075 - selftests: add missing test name in memory-hotplug test
5ff0c60b - selftests: fix memory-hotplug test
Testcase:
Run the script directly, it will fail when all memory blocks are busy. And it will try to unplug memory blocks in a fixed order.
Regression Potential:
Negligible, it's just affecting this specific test case among those testing tools.
CVE References
Changed in linux (Ubuntu): | |
status: | Incomplete → In Progress |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux (Ubuntu Zesty): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Artful): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux (Ubuntu Artful): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1710868
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.