diff options
author | Lecopzer Chen <lecopzer.chen@mediatek.com> | 2021-03-24 05:05:22 +0100 |
---|---|---|
committer | Catalin Marinas <catalin.marinas@arm.com> | 2021-03-29 13:35:05 +0200 |
commit | acc3042d62cb92c3776767f09f665511c903ef2d (patch) | |
tree | 55f73870a1020fb2602f7da641f7a2a6a8585e08 /Documentation/arm64 | |
parent | arm64: kaslr: support randomized module area with KASAN_VMALLOC (diff) | |
download | linux-acc3042d62cb92c3776767f09f665511c903ef2d.tar.xz linux-acc3042d62cb92c3776767f09f665511c903ef2d.zip |
arm64: Kconfig: select KASAN_VMALLOC if KANSAN_GENERIC is enabled
Before this patch, someone who wants to use VMAP_STACK when
KASAN_GENERIC enabled must explicitly select KASAN_VMALLOC.
>From Will's suggestion [1]:
> I would _really_ like to move to VMAP stack unconditionally, and
> that would effectively force KASAN_VMALLOC to be set if KASAN is in use
Because VMAP_STACK now depends on either HW_TAGS or KASAN_VMALLOC if
KASAN enabled, in order to make VMAP_STACK selected unconditionally,
we bind KANSAN_GENERIC and KASAN_VMALLOC together.
Note that SW_TAGS supports neither VMAP_STACK nor KASAN_VMALLOC now,
so this is the first step to make VMAP_STACK selected unconditionally.
Bind KANSAN_GENERIC and KASAN_VMALLOC together is supposed to cost more
memory at runtime, thus the alternative is using SW_TAGS KASAN instead.
[1]: https://lore.kernel.org/lkml/20210204150100.GE20815@willie-the-truck/
Suggested-by: Will Deacon <will@kernel.org>
Signed-off-by: Lecopzer Chen <lecopzer.chen@mediatek.com>
Link: https://lore.kernel.org/r/20210324040522.15548-6-lecopzer.chen@mediatek.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'Documentation/arm64')
0 files changed, 0 insertions, 0 deletions