Skip to content

Commit 52a2af4

Browse files
amlutoIngo Molnar
authored andcommitted
x86/mm/64: Stop using CR3.PCID == 0 in ASID-aware code
Putting the logical ASID into CR3's PCID bits directly means that we have two cases to consider separately: ASID == 0 and ASID != 0. This means that bugs that only hit in one of these cases trigger nondeterministically. There were some bugs like this in the past, and I think there's still one in current kernels. In particular, we have a number of ASID-unware code paths that save CR3, write some special value, and then restore CR3. This includes suspend/resume, hibernate, kexec, EFI, and maybe other things I've missed. This is currently dangerous: if ASID != 0, then this code sequence will leave garbage in the TLB tagged for ASID 0. We could potentially see corruption when switching back to ASID 0. In principle, an initialize_tlbstate_and_flush() call after these sequences would solve the problem, but EFI, at least, does not call this. (And it probably shouldn't -- initialize_tlbstate_and_flush() is rather expensive.) Signed-off-by: Andy Lutomirski <[email protected]> Cc: Borislav Petkov <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Thomas Gleixner <[email protected]> Link: http://lkml.kernel.org/r/cdc14bbe5d3c3ef2a562be09a6368ffe9bd947a6.1505663533.git.luto@kernel.org Signed-off-by: Ingo Molnar <[email protected]>
1 parent 47061a2 commit 52a2af4

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

arch/x86/include/asm/mmu_context.h

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -286,14 +286,31 @@ static inline bool arch_vma_access_permitted(struct vm_area_struct *vma,
286286
return __pkru_allows_pkey(vma_pkey(vma), write);
287287
}
288288

289+
/*
290+
* If PCID is on, ASID-aware code paths put the ASID+1 into the PCID
291+
* bits. This serves two purposes. It prevents a nasty situation in
292+
* which PCID-unaware code saves CR3, loads some other value (with PCID
293+
* == 0), and then restores CR3, thus corrupting the TLB for ASID 0 if
294+
* the saved ASID was nonzero. It also means that any bugs involving
295+
* loading a PCID-enabled CR3 with CR4.PCIDE off will trigger
296+
* deterministically.
297+
*/
298+
289299
static inline unsigned long build_cr3(struct mm_struct *mm, u16 asid)
290300
{
291-
return __sme_pa(mm->pgd) | asid;
301+
if (static_cpu_has(X86_FEATURE_PCID)) {
302+
VM_WARN_ON_ONCE(asid > 4094);
303+
return __sme_pa(mm->pgd) | (asid + 1);
304+
} else {
305+
VM_WARN_ON_ONCE(asid != 0);
306+
return __sme_pa(mm->pgd);
307+
}
292308
}
293309

294310
static inline unsigned long build_cr3_noflush(struct mm_struct *mm, u16 asid)
295311
{
296-
return __sme_pa(mm->pgd) | asid | CR3_NOFLUSH;
312+
VM_WARN_ON_ONCE(asid > 4094);
313+
return __sme_pa(mm->pgd) | (asid + 1) | CR3_NOFLUSH;
297314
}
298315

299316
/*

0 commit comments

Comments
 (0)