[Bug 1816425] Re: Use memblock quirk instead of delayed allocation for GICv3 LPI tables

** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1816425

Title:
Use memblock quirk instead of delayed allocation for GICv3 LPI tables

Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed

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_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \
sudo tee /etc/default/grub.d/kdump-tools.cfg
sudo update-grub
sudo reboot
echo 1 | sudo tee /proc/sys/kernel/sysrq
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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816425/+subscriptions