From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Nick Hu <nickhu@andestech.com>,
glider@google.com, dvyukov@google.com, corbet@lwn.net,
paul.walmsley@sifive.com, palmer@sifive.com,
aou@eecs.berkeley.edu, tglx@linutronix.de,
gregkh@linuxfoundation.org, alankao@andestech.com,
Anup.Patel@wdc.com, atish.patra@wdc.com,
kasan-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-mm@kvack.org, green.hu@gmail.com
Subject: Re: [PATCH v4 1/3] kasan: No KASAN's memmove check if archs don't have it.
Date: Mon, 18 Nov 2019 19:22:23 +0300 [thread overview]
Message-ID: <73f11f1e-6df7-c217-e05d-049d04717600@virtuozzo.com> (raw)
In-Reply-To: <20191028024101.26655-2-nickhu@andestech.com>
On 10/28/19 5:40 AM, Nick Hu wrote:
> 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@andestech.com>
> ---
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-11-18 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 2:40 [PATCH v4 0/3] KASAN support for RISC-V Nick Hu
2019-10-28 2:40 ` [PATCH v4 1/3] kasan: No KASAN's memmove check if archs don't have it Nick Hu
2019-11-17 4:57 ` Paul Walmsley
2019-11-18 8:41 ` Dmitry Vyukov
2019-11-18 16:22 ` Andrey Ryabinin [this message]
2019-10-28 2:41 ` [PATCH v4 2/3] riscv: Add KASAN support Nick Hu
2019-10-28 2:41 ` [PATCH v4 3/3] kasan: Add riscv to KASAN documentation Nick Hu
2019-10-28 7:01 ` [PATCH v4 0/3] KASAN support for RISC-V Greentime Hu
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=73f11f1e-6df7-c217-e05d-049d04717600@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=Anup.Patel@wdc.com \
--cc=alankao@andestech.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=green.hu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nickhu@andestech.com \
--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).