Use memblock quirk instead of delayed allocation for GICv3 LPI tables
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Committed
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The fix for LP: #1806766 has the issue that the persistent memory reservations for the GICv3 LPI tables may have been allocated an overwritten by the time we get to reserving them. This can continue to break kdump in certain conditions.
[Test Case]
sudo apt install linux-crashdump
echo 'GRUB_CMDLINE_
sudo tee /etc/default/
sudo update-grub
sudo reboot
echo 1 | sudo tee /proc/sys/
echo c | sudo tee /proc/sysrq-trigger
[Fix]
582a32e708823 efi/arm: Revert "Defer persistent reservations until after paging_init()"
8a5b403d71aff arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve table
[Regression Risk]
The change in reserved regions only impacts arm64.
Changed in linux (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Disco): | |
status: | New → In Progress |
Changed in linux (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Disco): | |
status: | Fix Committed → Won't Fix |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- cosmic' to 'verification- done-cosmic' . If the problem still exists, change the tag 'verification- needed- cosmic' to 'verification- failed- cosmic' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!