From: Lecopzer Chen <lecopzer@gmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org
Cc: dan.j.williams@intel.com, aryabinin@virtuozzo.com,
glider@google.com, dvyukov@google.com, akpm@linux-foundation.org,
linux-mediatek@lists.infradead.org, yj.chiang@mediatek.com,
will@kernel.org, catalin.marinas@arm.com,
Lecopzer Chen <lecopzer@gmail.com>,
Lecopzer Chen <lecopzer.chen@mediatek.com>
Subject: [PATCH 0/3] arm64: kasan: support CONFIG_KASAN_VMALLOC
Date: Mon, 4 Jan 2021 01:11:34 +0800 [thread overview]
Message-ID: <20210103171137.153834-1-lecopzer@gmail.com> (raw)
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@mediatek.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
next reply other threads:[~2021-01-03 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 17:11 Lecopzer Chen [this message]
2021-01-03 17:11 ` [PATCH 1/3] arm64: kasan: don't populate vmalloc area for CONFIG_KASAN_VMALLOC Lecopzer Chen
2021-01-03 17:11 ` [PATCH 2/3] arm64: kasan: abstract _text and _end to KERNEL_START/END Lecopzer Chen
2021-01-03 17:11 ` [PATCH 3/3] arm64: Kconfig: support CONFIG_KASAN_VMALLOC Lecopzer Chen
2021-01-08 18:29 ` Andrey Konovalov
2021-01-09 7:26 ` Lecopzer Chen
2021-01-08 18:30 ` [PATCH 0/3] arm64: kasan: " Andrey Konovalov
2021-01-08 18:41 ` Ard Biesheuvel
2021-01-09 10:02 ` Lecopzer Chen
2021-01-08 18:37 ` Andrey Konovalov
2021-01-09 7:34 ` 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=20210103171137.153834-1-lecopzer@gmail.com \
--to=lecopzer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).