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)
committerJianxin Pan <jianxin.pan@amlogic.com>
Thu, 9 May 2019 09:46:38 +0000 (02:46 -0700)
commit9ddd6cd4c8623ee31f1459ee3812e22291c2a2a3
tree8dc5c5dc6cdf44d7e61e096f9fb3595862748c6c
parent32dd894674ecaa380593c33aa0c6ca8cba5bc324
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