percpu: Separate decrypted varaibles anytime encryption can be enabled
commit264b0d2beeupstream. CONFIG_VIRTUALIZATION may not be enabled for memory encrypted guests. If disabled, decrypted per-CPU variables may end up sharing the same page with variables that should be left encrypted. Always separate per-CPU variables that should be decrypted into their own page anytime memory encryption can be enabled in the guest rather than rely on any other config option that may not be enabled. Fixes:ac26963a11("percpu: Introduce DEFINE_PER_CPU_DECRYPTED") Cc: stable@vger.kernel.org # 4.15+ Signed-off-by: Erdem Aktas <erdemaktas@google.com> Signed-off-by: David Rientjes <rientjes@google.com> Signed-off-by: Dennis Zhou <dennis@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
abc51506fc
commit
a5d0c3ff65
1 changed files with 1 additions and 2 deletions
|
|
@ -176,8 +176,7 @@
|
|||
* Declaration/definition used for per-CPU variables that should be accessed
|
||||
* as decrypted when memory encryption is enabled in the guest.
|
||||
*/
|
||||
#if defined(CONFIG_VIRTUALIZATION) && defined(CONFIG_AMD_MEM_ENCRYPT)
|
||||
|
||||
#ifdef CONFIG_AMD_MEM_ENCRYPT
|
||||
#define DECLARE_PER_CPU_DECRYPTED(type, name) \
|
||||
DECLARE_PER_CPU_SECTION(type, name, "..decrypted")
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue