correctly parse PMEM memory ranges to pass it to the kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre | ||
Zesty |
Triaged
|
High
|
Mathieu Trudel-Lapierre | ||
Artful |
Fix Released
|
Undecided
|
Unassigned | ||
grub2-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
New
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
If trying to boot a system with PMEM:
"Unknown memory type 14, considering reserved"
The system will then not have access to EFIPresistentMemory ranges, because grub could not hand them over to the kernel to use. The resulting system would be missing a /dev/pmemN device.
Grub requires 4 cherry-picked commits:
- debian/
- debian/
- debian/
- debian/
[Test case]
- Boot PMEM-enabled system with updated grub
[Regression Potential]
This changes handling of memory ranges in grub, and may lead to incorrectly passing memory to the kernel, or otherwise allowing allocation of memory within reserved ranges. This would typically lead to a failure to boot the kernel, or missing memory-based devices (such a missing /dev/pmem0).
Changed in grub2 (Ubuntu Artful): | |
status: | New → Fix Released |
Changed in grub2 (Ubuntu Xenial): | |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in grub2 (Ubuntu Zesty): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in grub2 (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Can you expand on the test case to explain how to configure such a pmem-enabled system?