From: Nick Hu <nickhu@andestech.com>
To: <alankao@andestech.com>, <paul.walmsley@sifive.com>,
<palmer@sifive.com>, <aou@eecs.berkeley.edu>,
<aryabinin@virtuozzo.com>, <glider@google.com>,
<dvyukov@google.com>, <alexios.zavras@intel.com>,
<allison@lohutok.net>, <Anup.Patel@wdc.com>, <tglx@linutronix.de>,
<gregkh@linuxfoundation.org>, <atish.patra@wdc.com>,
<kstewart@linuxfoundation.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kasan-dev@googlegroups.com>,
<linux-mm@kvack.org>
Cc: Nick Hu <nickhu@andestech.com>
Subject: [PATCH v2 1/2] kasan: Archs don't check memmove if not support it.
Date: Wed, 2 Oct 2019 14:16:04 +0800 [thread overview]
Message-ID: <c9fa9eb25a5c0b1f733494dfd439f056c6e938fd.1569995450.git.nickhu@andestech.com> (raw)
In-Reply-To: <cover.1569995450.git.nickhu@andestech.com>
Skip the memmove checking for those archs who don't support it.
Signed-off-by: Nick Hu <nickhu@andestech.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-10-02 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 6:16 [PATCH v2 0/2] KASAN support for RISC-V Nick Hu
2019-10-02 6:16 ` Nick Hu [this message]
2019-10-02 6:16 ` [PATCH v2 2/2] riscv: Add KASAN support Nick Hu
2019-10-02 10:55 ` Andrey Konovalov
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=c9fa9eb25a5c0b1f733494dfd439f056c6e938fd.1569995450.git.nickhu@andestech.com \
--to=nickhu@andestech.com \
--cc=Anup.Patel@wdc.com \
--cc=alankao@andestech.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=aou@eecs.berkeley.edu \
--cc=aryabinin@virtuozzo.com \
--cc=atish.patra@wdc.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/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).