[SRU][Q:linux-aws][PATCH 0/1] SEV-SNP instances on AWS fail to boot

[Magali Lemes]

BugLink: https://bugs.launchpad.net/bugs/2137714

[Impact]
AWS instances with SEV-SNP enabled running the 6.17 kernel fail to boot
following upstream commit 81256a50aa0f ("x86/mm: Make memremap(MEMREMAP_WB) map
memory as encrypted by default"). The failure occurs because the vmgenid
driver relies on memory that must be shared, but is now mapped as encrypted by
default.

[Fix]
Clean cherry-pick of bb9ff576fdff ("virt: vmgenid: remap memory as decrypted")
from linux-next.

[Test Plan]
Compile the kernel with this patch applied and boot test on AWS c7a.8xlarge
instances with SEV-SNP enabled and disabled, verifying that the system boots
successfully in both configurations.

[Where problems could occur]
This patch only touches the vmgenid driver, and only affects the memory
attributes of the vmgenid mapping. However, incorrect assumptions about the
sharing requirements of the vmgenid memory region could potentially lead to
loss of vmgenid functionality or boot failures.

Vitaly Kuznetsov (1):
  virt: vmgenid: remap memory as decrypted

 drivers/virt/vmgenid.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
2.34.1