[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210103171137.153834-1-lecopzer@gmail.com>
Date: Mon, 4 Jan 2021 01:11:34 +0800
From: Lecopzer Chen <lecopzer@...il.com>
To: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
kasan-dev@...glegroups.com, linux-arm-kernel@...ts.infradead.org
Cc: dan.j.williams@...el.com, aryabinin@...tuozzo.com,
glider@...gle.com, dvyukov@...gle.com, akpm@...ux-foundation.org,
linux-mediatek@...ts.infradead.org, yj.chiang@...iatek.com,
will@...nel.org, catalin.marinas@....com,
Lecopzer Chen <lecopzer@...il.com>,
Lecopzer Chen <lecopzer.chen@...iatek.com>
Subject: [PATCH 0/3] arm64: kasan: support CONFIG_KASAN_VMALLOC
Linux supports KAsan for VMALLOC since commit 3c5c3cfb9ef4da9
("kasan: support backing vmalloc space with real shadow memory")
Acroding to how x86 ported it [1], they early allocated p4d and pgd,
but in arm64 I just simulate how KAsan supports MODULES_VADDR in arm64
by not to populate the vmalloc area except for kimg address.
Test environment:
4G and 8G Qemu virt,
39-bit VA + 4k PAGE_SIZE with 3-level page table,
test by lib/test_kasan.ko and lib/test_kasan_module.ko
It also works in Kaslr with CONFIG_RANDOMIZE_MODULE_REGION_FULL,
but not test for HW_TAG(I have no proper device), thus keep
HW_TAG and KASAN_VMALLOC mutual exclusion until confirming
the functionality.
[1]: commit 0609ae011deb41c ("x86/kasan: support KASAN_VMALLOC")
Signed-off-by: Lecopzer Chen <lecopzer.chen@...iatek.com>
Lecopzer Chen (3):
arm64: kasan: don't populate vmalloc area for CONFIG_KASAN_VMALLOC
arm64: kasan: abstract _text and _end to KERNEL_START/END
arm64: Kconfig: support CONFIG_KASAN_VMALLOC
arch/arm64/Kconfig | 1 +
arch/arm64/mm/kasan_init.c | 29 +++++++++++++++++++++--------
2 files changed, 22 insertions(+), 8 deletions(-)
--
2.25.1
Powered by blists - more mailing lists