From: Alexander A Sverdlin <alexander.sverdlin@nokia.com> To: kasan-dev@googlegroups.com Cc: Alexander Sverdlin <alexander.sverdlin@nokia.com>, Russell King <linux@armlinux.org.uk>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Alexander Potapenko <glider@google.com>, Andrey Konovalov <andreyknvl@gmail.com>, Dmitry Vyukov <dvyukov@google.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 1/2] ARM: kasan: Support CONFIG_KASAN_VMALLOC Date: Fri, 6 May 2022 08:01:12 +0200 [thread overview] Message-ID: <20220506060113.14881-1-alexander.sverdlin@nokia.com> (raw) From: Alexander Sverdlin <alexander.sverdlin@nokia.com> Create KASAN mapping between VMALLOC_START and VMALLOC_END instead of early shadow if KASAN_VMALLOC is configured. Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nokia.com> --- arch/arm/Kconfig | 1 + arch/arm/mm/kasan_init.c | 7 ++++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index 2e8091e..f440cf5 100644 --- a/arch/arm/Kconfig +++ b/arch/arm/Kconfig @@ -75,6 +75,7 @@ config ARM select HAVE_ARCH_KFENCE if MMU && !XIP_KERNEL select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU select HAVE_ARCH_KASAN if MMU && !XIP_KERNEL + select HAVE_ARCH_KASAN_VMALLOC if HAVE_ARCH_KASAN select HAVE_ARCH_MMAP_RND_BITS if MMU select HAVE_ARCH_PFN_VALID select HAVE_ARCH_SECCOMP diff --git a/arch/arm/mm/kasan_init.c b/arch/arm/mm/kasan_init.c index 5ad0d6c5..c2f49f7 100644 --- a/arch/arm/mm/kasan_init.c +++ b/arch/arm/mm/kasan_init.c @@ -236,7 +236,12 @@ void __init kasan_init(void) clear_pgds(KASAN_SHADOW_START, KASAN_SHADOW_END); - kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_START), + if (IS_ENABLED(CONFIG_KASAN_VMALLOC)) + create_mapping((void *)VMALLOC_START, (void *)VMALLOC_END); + else + kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_START), + kasan_mem_to_shadow((void *)VMALLOC_END)); + kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_END), kasan_mem_to_shadow((void *)-1UL) + 1); for_each_mem_range(i, &pa_start, &pa_end) { -- 2.10.2
WARNING: multiple messages have this Message-ID (diff)
From: Alexander A Sverdlin <alexander.sverdlin@nokia.com> To: kasan-dev@googlegroups.com Cc: Alexander Sverdlin <alexander.sverdlin@nokia.com>, Russell King <linux@armlinux.org.uk>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Alexander Potapenko <glider@google.com>, Andrey Konovalov <andreyknvl@gmail.com>, Dmitry Vyukov <dvyukov@google.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 1/2] ARM: kasan: Support CONFIG_KASAN_VMALLOC Date: Fri, 6 May 2022 08:01:12 +0200 [thread overview] Message-ID: <20220506060113.14881-1-alexander.sverdlin@nokia.com> (raw) From: Alexander Sverdlin <alexander.sverdlin@nokia.com> Create KASAN mapping between VMALLOC_START and VMALLOC_END instead of early shadow if KASAN_VMALLOC is configured. Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nokia.com> --- arch/arm/Kconfig | 1 + arch/arm/mm/kasan_init.c | 7 ++++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index 2e8091e..f440cf5 100644 --- a/arch/arm/Kconfig +++ b/arch/arm/Kconfig @@ -75,6 +75,7 @@ config ARM select HAVE_ARCH_KFENCE if MMU && !XIP_KERNEL select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU select HAVE_ARCH_KASAN if MMU && !XIP_KERNEL + select HAVE_ARCH_KASAN_VMALLOC if HAVE_ARCH_KASAN select HAVE_ARCH_MMAP_RND_BITS if MMU select HAVE_ARCH_PFN_VALID select HAVE_ARCH_SECCOMP diff --git a/arch/arm/mm/kasan_init.c b/arch/arm/mm/kasan_init.c index 5ad0d6c5..c2f49f7 100644 --- a/arch/arm/mm/kasan_init.c +++ b/arch/arm/mm/kasan_init.c @@ -236,7 +236,12 @@ void __init kasan_init(void) clear_pgds(KASAN_SHADOW_START, KASAN_SHADOW_END); - kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_START), + if (IS_ENABLED(CONFIG_KASAN_VMALLOC)) + create_mapping((void *)VMALLOC_START, (void *)VMALLOC_END); + else + kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_START), + kasan_mem_to_shadow((void *)VMALLOC_END)); + kasan_populate_early_shadow(kasan_mem_to_shadow((void *)VMALLOC_END), kasan_mem_to_shadow((void *)-1UL) + 1); for_each_mem_range(i, &pa_start, &pa_end) { -- 2.10.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-06 6:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-06 6:01 Alexander A Sverdlin [this message] 2022-05-06 6:01 ` [PATCH 1/2] ARM: kasan: Support CONFIG_KASAN_VMALLOC Alexander A Sverdlin 2022-05-06 6:01 ` [PATCH 2/2] ARM: kasan: Fix compatibility with ARM_MODULE_PLTS Alexander A Sverdlin 2022-05-06 6:01 ` Alexander A Sverdlin -- strict thread matches above, loose matches on Subject: below -- 2022-01-18 9:44 [PATCH 0/2] arm: kasan: support CONFIG_KASAN_VMALLOC Lecopzer Chen 2022-01-18 9:44 ` [PATCH 1/2] " Lecopzer Chen 2022-01-18 9:44 ` 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=20220506060113.14881-1-alexander.sverdlin@nokia.com \ --to=alexander.sverdlin@nokia.com \ --cc=andreyknvl@gmail.com \ --cc=dvyukov@google.com \ --cc=glider@google.com \ --cc=kasan-dev@googlegroups.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=ryabinin.a.a@gmail.com \ --cc=vincenzo.frascino@arm.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.