aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/caching/backend-api.rst
diff options
context:
space:
mode:
authorPawan Gupta <[email protected]>2022-04-05 00:35:45 +0000
committerLinus Torvalds <[email protected]>2022-04-05 17:18:31 +0000
commite2a1256b17b16f9b9adf1b6fea56819e7b68e463 (patch)
treeb3fd79e653f2f7a31c0eddacb8f797890e7ff35a /Documentation/filesystems/caching/backend-api.rst
parentx86/pm: Save the MSR validity status at context setup (diff)
downloadkernel-e2a1256b17b16f9b9adf1b6fea56819e7b68e463.tar.gz
kernel-e2a1256b17b16f9b9adf1b6fea56819e7b68e463.zip
x86/speculation: Restore speculation related MSRs during S3 resume
After resuming from suspend-to-RAM, the MSRs that control CPU's speculative execution behavior are not being restored on the boot CPU. These MSRs are used to mitigate speculative execution vulnerabilities. Not restoring them correctly may leave the CPU vulnerable. Secondary CPU's MSRs are correctly being restored at S3 resume by identify_secondary_cpu(). During S3 resume, restore these MSRs for boot CPU when restoring its processor state. Fixes: 772439717dbf ("x86/bugs/intel: Set proper CPU features and setup RDS") Reported-by: Neelima Krishnan <[email protected]> Signed-off-by: Pawan Gupta <[email protected]> Tested-by: Neelima Krishnan <[email protected]> Acked-by: Borislav Petkov <[email protected]> Reviewed-by: Dave Hansen <[email protected]> Cc: [email protected] Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'Documentation/filesystems/caching/backend-api.rst')
0 files changed, 0 insertions, 0 deletions