kasan: rebuild address layout after vmalloc increased [1/1]
authorTao Zeng <tao.zeng@amlogic.com>
Tue, 7 May 2019 02:51:42 +0000 (10:51 +0800)
committerNick Xie <nick@khadas.com>
Mon, 5 Aug 2019 06:31:48 +0000 (14:31 +0800)
commit25850ef473b38097298f544448083e276a416af1
tree93518c8670c98e4ebbbefff1234f67f1bb8e8630
parent04699e52508c432297ec9292941dec7bf858b7e9
kasan: rebuild address layout after vmalloc increased [1/1]

PD#SWPL-8132

Problem:
In Jira TV-5143, final fix change have increased 128MB address space
for vmalloc. Because binder wasted too many vmalloc space but it's
hard to fix it in kernel side.
Due to incease of vmalloc address space, old design of address space
layout for KASAN32 is not suitable after this change. So we need to
change memory layout to fix this problem and let KASAN can running OK
again.

Solution:
1, rebuild address space layout for kasan
2, make kasan compatible with vmap stack config

Verify:
p212

Change-Id: I2ce8a840df0ce1fcda61ebeb14a64b1d609719ca
Signed-off-by: Tao Zeng <tao.zeng@amlogic.com>
12 files changed:
arch/arm/Kconfig
arch/arm/Makefile
arch/arm/include/asm/kasan.h
arch/arm/include/asm/memory.h
arch/arm/kernel/unwind.c
arch/arm/mm/kasan_init.c
arch/arm64/include/asm/kasan.h
arch/arm64/mm/kasan_init.c
drivers/amlogic/memory_ext/Kconfig
drivers/amlogic/memory_ext/vmap_stack.c
include/linux/amlogic/vmap_stack.h
mm/kasan/report.c