forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
powerpc: Book3S 64-bit outline-only KASAN support
Implement a limited form of KASAN for Book3S 64-bit machines running under the Radix MMU, supporting only outline mode. - Enable the compiler instrumentation to check addresses and maintain the shadow region. (This is the guts of KASAN which we can easily reuse.) - Require kasan-vmalloc support to handle modules and anything else in vmalloc space. - KASAN needs to be able to validate all pointer accesses, but we can't instrument all kernel addresses - only linear map and vmalloc. On boot, set up a single page of read-only shadow that marks all iomap and vmemmap accesses as valid. - Document KASAN in powerpc docs. Background ---------- KASAN support on Book3S is a bit tricky to get right: - It would be good to support inline instrumentation so as to be able to catch stack issues that cannot be caught with outline mode. - Inline instrumentation requires a fixed offset. - Book3S runs code with translations off ("real mode") during boot, including a lot of generic device-tree parsing code which is used to determine MMU features. [ppc64 mm note: The kernel installs a linear mapping at effective address c000...-c008.... This is a one-to-one mapping with physical memory from 0000... onward. Because of how memory accesses work on powerpc 64-bit Book3S, a kernel pointer in the linear map accesses the same memory both with translations on (accessing as an 'effective address'), and with translations off (accessing as a 'real address'). This works in both guests and the hypervisor. For more details, see s5.7 of Book III of version 3 of the ISA, in particular the Storage Control Overview, s5.7.3, and s5.7.5 - noting that this KASAN implementation currently only supports Radix.] - Some code - most notably a lot of KVM code - also runs with translations off after boot. - Therefore any offset has to point to memory that is valid with translations on or off. One approach is just to give up on inline instrumentation. This way boot-time checks can be delayed until after the MMU is set is up, and we can just not instrument any code that runs with translations off after booting. Take this approach for now and require outline instrumentation. Previous attempts allowed inline instrumentation. However, they came with some unfortunate restrictions: only physically contiguous memory could be used and it had to be specified at compile time. Maybe we can do better in the future. [paulus@ozlabs.org - Rebased onto 5.17. Note that a kernel with CONFIG_KASAN=y will crash during boot on a machine using HPT translation because not all the entry points to the generic KASAN code are protected with a call to kasan_arch_is_ready().] Originally-by: Balbir Singh <bsingharora@gmail.com> # ppc64 out-of-line radix version Signed-off-by: Daniel Axtens <dja@axtens.net> Signed-off-by: Paul Mackerras <paulus@ozlabs.org> [mpe: Update copyright year and comment formatting] Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/YoTE69OQwiG7z+Gu@cleo
- Loading branch information
Showing
16 changed files
with
232 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,102 @@ | ||
// SPDX-License-Identifier: GPL-2.0 | ||
/* | ||
* KASAN for 64-bit Book3S powerpc | ||
* | ||
* Copyright 2019-2022, Daniel Axtens, IBM Corporation. | ||
*/ | ||
|
||
/* | ||
* ppc64 turns on virtual memory late in boot, after calling into generic code | ||
* like the device-tree parser, so it uses this in conjunction with a hook in | ||
* outline mode to avoid invalid access early in boot. | ||
*/ | ||
|
||
#define DISABLE_BRANCH_PROFILING | ||
|
||
#include <linux/kasan.h> | ||
#include <linux/printk.h> | ||
#include <linux/sched/task.h> | ||
#include <linux/memblock.h> | ||
#include <asm/pgalloc.h> | ||
|
||
DEFINE_STATIC_KEY_FALSE(powerpc_kasan_enabled_key); | ||
|
||
static void __init kasan_init_phys_region(void *start, void *end) | ||
{ | ||
unsigned long k_start, k_end, k_cur; | ||
void *va; | ||
|
||
if (start >= end) | ||
return; | ||
|
||
k_start = ALIGN_DOWN((unsigned long)kasan_mem_to_shadow(start), PAGE_SIZE); | ||
k_end = ALIGN((unsigned long)kasan_mem_to_shadow(end), PAGE_SIZE); | ||
|
||
va = memblock_alloc(k_end - k_start, PAGE_SIZE); | ||
for (k_cur = k_start; k_cur < k_end; k_cur += PAGE_SIZE, va += PAGE_SIZE) | ||
map_kernel_page(k_cur, __pa(va), PAGE_KERNEL); | ||
} | ||
|
||
void __init kasan_init(void) | ||
{ | ||
/* | ||
* We want to do the following things: | ||
* 1) Map real memory into the shadow for all physical memblocks | ||
* This takes us from c000... to c008... | ||
* 2) Leave a hole over the shadow of vmalloc space. KASAN_VMALLOC | ||
* will manage this for us. | ||
* This takes us from c008... to c00a... | ||
* 3) Map the 'early shadow'/zero page over iomap and vmemmap space. | ||
* This takes us up to where we start at c00e... | ||
*/ | ||
|
||
void *k_start = kasan_mem_to_shadow((void *)RADIX_VMALLOC_END); | ||
void *k_end = kasan_mem_to_shadow((void *)RADIX_VMEMMAP_END); | ||
phys_addr_t start, end; | ||
u64 i; | ||
pte_t zero_pte = pfn_pte(virt_to_pfn(kasan_early_shadow_page), PAGE_KERNEL); | ||
|
||
if (!early_radix_enabled()) { | ||
pr_warn("KASAN not enabled as it requires radix!"); | ||
return; | ||
} | ||
|
||
for_each_mem_range(i, &start, &end) | ||
kasan_init_phys_region((void *)start, (void *)end); | ||
|
||
for (i = 0; i < PTRS_PER_PTE; i++) | ||
__set_pte_at(&init_mm, (unsigned long)kasan_early_shadow_page, | ||
&kasan_early_shadow_pte[i], zero_pte, 0); | ||
|
||
for (i = 0; i < PTRS_PER_PMD; i++) | ||
pmd_populate_kernel(&init_mm, &kasan_early_shadow_pmd[i], | ||
kasan_early_shadow_pte); | ||
|
||
for (i = 0; i < PTRS_PER_PUD; i++) | ||
pud_populate(&init_mm, &kasan_early_shadow_pud[i], | ||
kasan_early_shadow_pmd); | ||
|
||
/* map the early shadow over the iomap and vmemmap space */ | ||
kasan_populate_early_shadow(k_start, k_end); | ||
|
||
/* mark early shadow region as RO and wipe it */ | ||
zero_pte = pfn_pte(virt_to_pfn(kasan_early_shadow_page), PAGE_KERNEL_RO); | ||
for (i = 0; i < PTRS_PER_PTE; i++) | ||
__set_pte_at(&init_mm, (unsigned long)kasan_early_shadow_page, | ||
&kasan_early_shadow_pte[i], zero_pte, 0); | ||
|
||
/* | ||
* clear_page relies on some cache info that hasn't been set up yet. | ||
* It ends up looping ~forever and blows up other data. | ||
* Use memset instead. | ||
*/ | ||
memset(kasan_early_shadow_page, 0, PAGE_SIZE); | ||
|
||
static_branch_inc(&powerpc_kasan_enabled_key); | ||
|
||
/* Enable error messages */ | ||
init_task.kasan_depth = 0; | ||
pr_info("KASAN init done\n"); | ||
} | ||
|
||
void __init kasan_late_init(void) { } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters