x86/mm: Handle decryption/re-encryption of bss_decrypted consistently
authorMichael Kelley <mikelley@microsoft.com>
Thu, 9 Mar 2023 02:40:05 +0000 (18:40 -0800)
committerBorislav Petkov (AMD) <bp@alien8.de>
Mon, 27 Mar 2023 07:23:21 +0000 (09:23 +0200)
commitc7b5254bd802ee3868f1c59333545272dc700d6d
treeebecf38fb6074e6984b192fa56c6fb4f6a0d2af9
parentd33ddc92db8a61416473ff3d7f1c621c50733dc0
x86/mm: Handle decryption/re-encryption of bss_decrypted consistently

sme_postprocess_startup() decrypts the bss_decrypted section when
sme_me_mask is non-zero.

mem_encrypt_free_decrypted_mem() re-encrypts the unused portion based
on CC_ATTR_MEM_ENCRYPT.

In a Hyper-V guest VM using vTOM, these conditions are not equivalent
as sme_me_mask is always zero when using vTOM. Consequently,
mem_encrypt_free_decrypted_mem() attempts to re-encrypt memory that was
never decrypted.

So check sme_me_mask in mem_encrypt_free_decrypted_mem() too.

Hyper-V guests using vTOM don't need the bss_decrypted section to be
decrypted, so skipping the decryption/re-encryption doesn't cause a
problem.

Signed-off-by: Michael Kelley <mikelley@microsoft.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/1678329614-3482-5-git-send-email-mikelley@microsoft.com
arch/x86/mm/mem_encrypt_amd.c