[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220227134726.27584-1-lecopzer.chen@mediatek.com>
Date: Sun, 27 Feb 2022 21:47:24 +0800
From: Lecopzer Chen <lecopzer.chen@...iatek.com>
To: <linus.walleij@...aro.org>, <linux-kernel@...r.kernel.org>
CC: <andreyknvl@...il.com>, <anshuman.khandual@....com>,
<ardb@...nel.org>, <arnd@...db.de>, <dvyukov@...gle.com>,
<geert+renesas@...der.be>, <glider@...gle.com>,
<kasan-dev@...glegroups.com>, <lecopzer.chen@...iatek.com>,
<linux-arm-kernel@...ts.infradead.org>, <linux@...linux.org.uk>,
<lukas.bulwahn@...il.com>, <mark.rutland@....com>,
<masahiroy@...nel.org>, <matthias.bgg@...il.com>,
<rmk+kernel@...linux.org.uk>, <ryabinin.a.a@...il.com>,
<yj.chiang@...iatek.com>
Subject: [PATCH v3 0/2] arm: kasan: support CONFIG_KASAN_VMALLOC
Since the framework of KASAN_VMALLOC is well-developed,
It's easy to support for ARM that simply not to map shadow of VMALLOC
area on kasan_init.
Since the virtual address of vmalloc for Arm is also between
MODULE_VADDR and 0x100000000 (ZONE_HIGHMEM), which means the shadow
address has already included between KASAN_SHADOW_START and
KASAN_SHADOW_END.
Thus we need to change nothing for memory map of Arm.
This can fix ARM_MODULE_PLTS with KASan, support KASan for higmem
and provide the first step to support CONFIG_VMAP_STACK with Arm.
Test on
1. Qemu with memory 2G and vmalloc=500M for 3G/1G mapping.
2. Qemu with memory 2G and vmalloc=500M for 3G/1G mapping + LPAE.
3. Qemu with memory 2G and vmalloc=500M for 2G/2G mapping.
v3:
rebase on 5.17-rc5.
Add simple doc for "arm: kasan: support CONFIG_KASAN_VMALLOC"
Tweak commit message.
v2:
rebase on 5.17-rc3
Lecopzer Chen (2):
arm: kasan: support CONFIG_KASAN_VMALLOC
arm: kconfig: fix MODULE_PLTS for KASAN with KASAN_VMALLOC
arch/arm/Kconfig | 2 ++
arch/arm/include/asm/kasan_def.h | 11 ++++++++++-
arch/arm/mm/kasan_init.c | 6 +++++-
3 files changed, 17 insertions(+), 2 deletions(-)
--
2.25.1
Powered by blists - more mailing lists