-
Notifications
You must be signed in to change notification settings - Fork 53.6k
Commit
…x/kernel/git/tip/tip Pull x86 page table isolation fixes from Thomas Gleixner: "A couple of urgent fixes for PTI: - Fix a PTE mismatch between user and kernel visible mapping of the cpu entry area (differs vs. the GLB bit) and causes a TLB mismatch MCE on older AMD K8 machines - Fix the misplaced CR3 switch in the SYSCALL compat entry code which causes access to unmapped kernel memory resulting in double faults. - Fix the section mismatch of the cpu_tss_rw percpu storage caused by using a different mechanism for declaration and definition. - Two fixes for dumpstack which help to decode entry stack issues better - Enable PTI by default in Kconfig. We should have done that earlier, but it slipped through the cracks. - Exclude AMD from the PTI enforcement. Not necessarily a fix, but if AMD is so confident that they are not affected, then we should not burden users with the overhead" * 'x86-pti-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/process: Define cpu_tss_rw in same section as declaration x86/pti: Switch to kernel CR3 at early in entry_SYSCALL_compat() x86/dumpstack: Print registers for first stack frame x86/dumpstack: Fix partial register dumps x86/pti: Make sure the user/kernel PTEs match x86/cpu, x86/pti: Do not enable PTI on AMD processors x86/pti: Enable PTI by default
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -923,8 +923,8 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c) | |
|
||
setup_force_cpu_cap(X86_FEATURE_ALWAYS); | ||
|
||
/* Assume for now that ALL x86 CPUs are insecure */ | ||
setup_force_cpu_bug(X86_BUG_CPU_INSECURE); | ||
if (c->x86_vendor != X86_VENDOR_AMD) | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
DesmondFox
via email
|
||
setup_force_cpu_bug(X86_BUG_CPU_INSECURE); | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. |
||
|
||
fpu__init_system(c); | ||
|
||
|
1 comment
on commit 00a5ae2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The following CPUs also aren't affected because they don't do ANY speculation:
"Vortex86 SoC"
"SiS SiS SiS " (also for the first vortex86's)
Pre-2013 Atoms (i.e. up to n2800 but not n2807 etc)
Probably weird old ones like Rise mP6, etc
Nice job