[Hyper-V] Disable CONFIG_HOTPLUG_CPU in linux-azure
Bug #1776293 reported by
Joshua R. Poulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-azure (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Marcelo Cerri |
Bug Description
While Hyper-V may present all potential CPUs via ACPI MADT, CPU add/remove is not supported. This results in kernel data structures created for the largest potential size based on the number of CPUs when those CPUs will never be added during the time the guest is up (it can certainly be resized when it's down and deallocated). Please disable CONFIG_HOTPLUG_CPU in linux-azure.
CVE References
Changed in linux-azure (Ubuntu Bionic): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Marcelo Cerri (mhcerri) |
tags: | added: patch |
Changed in linux-azure (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Hi, Josh.
In order to disable CONFIG_HOTPLUG_CPU, we also need to turn off CONFIG_HIBERNATION, CONFIG_SUSPEND and everything that relies on them. Are you ok with that?
I'm attaching the patch with the config changes if you want to take a closer look at it.