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>, <corbet@lwn.net>,
<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-doc@vger.kernel.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 v3 0/3] KASAN support for RISC-V
Date: Tue, 8 Oct 2019 14:11:50 +0800 [thread overview]
Message-ID: <cover.1570514544.git.nickhu@andestech.com> (raw)
KASAN is an important runtime memory debugging feature in linux kernel
which can detect use-after-free and out-of-bounds problems.
Changes in v2:
- Remove the porting of memmove and exclude the check instead.
- Fix some code noted by Christoph Hellwig
Changes in v3:
- Update the KASAN documentation to mention that riscv is supported.
Nick Hu (3):
kasan: Archs don't check memmove if not support it.
riscv: Add KASAN support
kasan: Add riscv to KASAN documentation.
Documentation/dev-tools/kasan.rst | 4 +-
arch/riscv/Kconfig | 1 +
arch/riscv/include/asm/kasan.h | 27 ++++++++
arch/riscv/include/asm/pgtable-64.h | 5 ++
arch/riscv/include/asm/string.h | 9 +++
arch/riscv/kernel/head.S | 3 +
arch/riscv/kernel/riscv_ksyms.c | 2 +
arch/riscv/kernel/setup.c | 5 ++
arch/riscv/kernel/vmlinux.lds.S | 1 +
arch/riscv/lib/memcpy.S | 5 +-
arch/riscv/lib/memset.S | 5 +-
arch/riscv/mm/Makefile | 6 ++
arch/riscv/mm/kasan_init.c | 104 ++++++++++++++++++++++++++++
mm/kasan/common.c | 2 +
14 files changed, 173 insertions(+), 6 deletions(-)
create mode 100644 arch/riscv/include/asm/kasan.h
create mode 100644 arch/riscv/mm/kasan_init.c
--
2.17.0
WARNING: multiple messages have this Message-ID (diff)
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>, <corbet@lwn.net>,
<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-doc@vger.kernel.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 v3 0/3] KASAN support for RISC-V
Date: Tue, 8 Oct 2019 14:11:50 +0800 [thread overview]
Message-ID: <cover.1570514544.git.nickhu@andestech.com> (raw)
KASAN is an important runtime memory debugging feature in linux kernel
which can detect use-after-free and out-of-bounds problems.
Changes in v2:
- Remove the porting of memmove and exclude the check instead.
- Fix some code noted by Christoph Hellwig
Changes in v3:
- Update the KASAN documentation to mention that riscv is supported.
Nick Hu (3):
kasan: Archs don't check memmove if not support it.
riscv: Add KASAN support
kasan: Add riscv to KASAN documentation.
Documentation/dev-tools/kasan.rst | 4 +-
arch/riscv/Kconfig | 1 +
arch/riscv/include/asm/kasan.h | 27 ++++++++
arch/riscv/include/asm/pgtable-64.h | 5 ++
arch/riscv/include/asm/string.h | 9 +++
arch/riscv/kernel/head.S | 3 +
arch/riscv/kernel/riscv_ksyms.c | 2 +
arch/riscv/kernel/setup.c | 5 ++
arch/riscv/kernel/vmlinux.lds.S | 1 +
arch/riscv/lib/memcpy.S | 5 +-
arch/riscv/lib/memset.S | 5 +-
arch/riscv/mm/Makefile | 6 ++
arch/riscv/mm/kasan_init.c | 104 ++++++++++++++++++++++++++++
mm/kasan/common.c | 2 +
14 files changed, 173 insertions(+), 6 deletions(-)
create mode 100644 arch/riscv/include/asm/kasan.h
create mode 100644 arch/riscv/mm/kasan_init.c
--
2.17.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-10-08 6:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 6:11 Nick Hu [this message]
2019-10-08 6:11 ` [PATCH v3 0/3] KASAN support for RISC-V Nick Hu
2019-10-08 6:11 ` [PATCH v3 1/3] kasan: Archs don't check memmove if not support it Nick Hu
2019-10-08 6:11 ` Nick Hu
2019-10-16 19:23 ` Palmer Dabbelt
2019-10-16 19:23 ` Palmer Dabbelt
2019-10-17 10:39 ` Andrey Ryabinin
2019-10-17 10:39 ` Andrey Ryabinin
2019-10-18 2:58 ` Paul Walmsley
2019-10-18 2:58 ` Paul Walmsley
2019-10-22 2:09 ` Nick Hu
2019-10-22 2:09 ` Nick Hu
2019-10-08 6:11 ` [PATCH v3 2/3] riscv: Add KASAN support Nick Hu
2019-10-08 6:11 ` Nick Hu
2019-10-21 9:33 ` Greentime Hu
2019-10-21 9:33 ` Greentime Hu
2019-10-22 3:30 ` Nick Hu
2019-10-22 3:30 ` Nick Hu
2019-10-08 6:11 ` [PATCH v3 3/3] kasan: Add riscv to KASAN documentation Nick Hu
2019-10-08 6:11 ` Nick 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=cover.1570514544.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=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.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 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.