From: liuwenliang@huawei.com (Abbott Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] Enable KASan for arm
Date: Sun, 18 Mar 2018 20:53:42 +0800 [thread overview]
Message-ID: <20180318125342.4278-8-liuwenliang@huawei.com> (raw)
In-Reply-To: <20180318125342.4278-1-liuwenliang@huawei.com>
From: Andrey Ryabinin <a.ryabinin@samsung.com>
This patch enable kernel address sanitizer for arm.
Cc: Andrey Ryabinin <a.ryabinin@samsung.com>
Tested-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Abbott Liu <liuwenliang@huawei.com>
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 7e3d535..ac2287b 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -49,6 +49,7 @@ config ARM
select HAVE_ARCH_BITREVERSE if (CPU_32v7M || CPU_32v7) && !CPU_32v6
select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL && !CPU_ENDIAN_BE32 && MMU
select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU
+ select HAVE_ARCH_KASAN if MMU
select HAVE_ARCH_MMAP_RND_BITS if MMU
select HAVE_ARCH_SECCOMP_FILTER if (AEABI && !OABI_COMPAT)
select HAVE_ARCH_THREAD_STRUCT_WHITELIST
--
2.9.0
next prev parent reply other threads:[~2018-03-18 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 12:53 [PATCH v2 0/7] KASan for arm Abbott Liu
2018-03-18 12:53 ` [PATCH 1/7] 2 1-byte checks more safer for memory_is_poisoned_16 Abbott Liu
2018-03-18 13:21 ` Russell King - ARM Linux
2018-03-18 12:53 ` [PATCH 2/7] Add TTBR operator for kasan_init Abbott Liu
2018-03-18 12:53 ` [PATCH 3/7] Disable instrumentation for some code Abbott Liu
2018-03-19 8:38 ` Marc Zyngier
2018-03-18 12:53 ` [PATCH 4/7] Replace memory function for kasan Abbott Liu
2018-03-18 12:53 ` [PATCH 5/7] Define the virtual space of KASan's shadow region Abbott Liu
2018-03-18 12:53 ` [PATCH 6/7] Initialize the mapping of KASan shadow memory Abbott Liu
2018-03-18 12:53 ` Abbott Liu [this message]
2018-03-19 20:43 ` [PATCH 7/7] Enable KASan for arm kbuild test robot
2018-03-18 19:13 ` [PATCH v2 0/7] " Florian Fainelli
2018-03-19 18:29 ` Florian Fainelli
2018-03-25 23:58 ` Joel Stanley
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=20180318125342.4278-8-liuwenliang@huawei.com \
--to=liuwenliang@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).