From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <lecopzer.chen@mediatek.com>, <andreyknvl@gmail.com>,
<anshuman.khandual@arm.com>, <ardb@kernel.org>, <arnd@arndb.de>,
<dvyukov@google.com>, <geert+renesas@glider.be>,
<glider@google.com>, <kasan-dev@googlegroups.com>,
<linus.walleij@linaro.org>, <linux@armlinux.org.uk>,
<lukas.bulwahn@gmail.com>, <mark.rutland@arm.com>,
<masahiroy@kernel.org>, <matthias.bgg@gmail.com>,
<rmk+kernel@armlinux.org.uk>, <ryabinin.a.a@gmail.com>,
<yj.chiang@mediatek.com>
Subject: [PATCH v2 0/2] arm: kasan: support CONFIG_KASAN_VMALLOC
Date: Sat, 12 Feb 2022 15:47:45 +0800 [thread overview]
Message-ID: <20220212074747.10849-1-lecopzer.chen@mediatek.com> (raw)
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.
This can fix ARM_MODULE_PLTS with KASAN and provide first step
to support CONFIG_VMAP_STACK in ARM.
Patch base on v5.16
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.
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/mm/kasan_init.c | 6 +++++-
2 files changed, 7 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2022-02-12 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 7:47 Lecopzer Chen [this message]
2022-02-12 7:47 ` [PATCH v2 1/2] " Lecopzer Chen
2022-02-12 21:26 ` Linus Walleij
2022-02-13 16:06 ` Lecopzer Chen
2022-02-12 7:47 ` [PATCH v2 2/2] arm: kconfig: fix MODULE_PLTS for KASAN with KASAN_VMALLOC Lecopzer Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220212074747.10849-1-lecopzer.chen@mediatek.com \
--to=lecopzer.chen@mediatek.com \
--cc=andreyknvl@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=geert+renesas@glider.be \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas.bulwahn@gmail.com \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=ryabinin.a.a@gmail.com \
--cc=yj.chiang@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®