[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191028024101.26655-2-nickhu@andestech.com>
Date: Mon, 28 Oct 2019 10:40:59 +0800
From: Nick Hu <nickhu@...estech.com>
To: <aryabinin@...tuozzo.com>, <glider@...gle.com>,
<dvyukov@...gle.com>, <corbet@....net>, <paul.walmsley@...ive.com>,
<palmer@...ive.com>, <aou@...s.berkeley.edu>, <tglx@...utronix.de>,
<gregkh@...uxfoundation.org>, <alankao@...estech.com>,
<Anup.Patel@....com>, <atish.patra@....com>,
<kasan-dev@...glegroups.com>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
<linux-mm@...ck.org>, <green.hu@...il.com>
CC: Nick Hu <nickhu@...estech.com>
Subject: [PATCH v4 1/3] kasan: No KASAN's memmove check if archs don't have it.
If archs don't have memmove then the C implementation from lib/string.c is used,
and then it's instrumented by compiler. So there is no need to add KASAN's
memmove to manual checks.
Signed-off-by: Nick Hu <nickhu@...estech.com>
---
mm/kasan/common.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/kasan/common.c b/mm/kasan/common.c
index 6814d6d6a023..897f9520bab3 100644
--- a/mm/kasan/common.c
+++ b/mm/kasan/common.c
@@ -107,6 +107,7 @@ void *memset(void *addr, int c, size_t len)
return __memset(addr, c, len);
}
+#ifdef __HAVE_ARCH_MEMMOVE
#undef memmove
void *memmove(void *dest, const void *src, size_t len)
{
@@ -115,6 +116,7 @@ void *memmove(void *dest, const void *src, size_t len)
return __memmove(dest, src, len);
}
+#endif
#undef memcpy
void *memcpy(void *dest, const void *src, size_t len)
--
2.17.0
Powered by blists - more mailing lists