From: Nick Hu <nickhu@andestech.com>
To: <alankao@andestech.com>, <paul.walmsley@sifive.com>,
<palmer@sifive.com>, <aou@eecs.berkeley.edu>,
<green.hu@gmail.com>, <deanbo422@gmail.com>, <tglx@linutronix.de>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<aryabinin@virtuozzo.com>, <glider@google.com>,
<dvyukov@google.com>, <Anup.Patel@wdc.com>,
<gregkh@linuxfoundation.org>, <alexios.zavras@intel.com>,
<atish.patra@wdc.com>, <zong@andestech.com>,
<kasan-dev@googlegroups.com>
Cc: Nick Hu <nickhu@andestech.com>
Subject: [PATCH 0/2] KASAN support for RISC-V
Date: Wed, 7 Aug 2019 15:19:13 +0800 [thread overview]
Message-ID: <cover.1565161957.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.
There are two patches in this letter:
1. Porting the memmove string operation.
2. Porting the feature KASAN.
Nick Hu (2):
riscv: Add memmove string operation.
riscv: Add KASAN support
arch/riscv/Kconfig | 2 +
arch/riscv/include/asm/kasan.h | 26 +++++++++
arch/riscv/include/asm/pgtable-64.h | 5 ++
arch/riscv/include/asm/string.h | 10 ++++
arch/riscv/kernel/head.S | 3 +
arch/riscv/kernel/riscv_ksyms.c | 4 ++
arch/riscv/kernel/setup.c | 9 +++
arch/riscv/kernel/vmlinux.lds.S | 1 +
arch/riscv/lib/Makefile | 1 +
arch/riscv/lib/memcpy.S | 5 +-
arch/riscv/lib/memmove.S | 64 ++++++++++++++++++++++
arch/riscv/lib/memset.S | 5 +-
arch/riscv/mm/Makefile | 6 ++
arch/riscv/mm/kasan_init.c | 102 +++++++++++++++++++++++++++++++++++
14 files changed, 239 insertions(+), 4 deletions(-)
create mode 100644 arch/riscv/include/asm/kasan.h
create mode 100644 arch/riscv/lib/memmove.S
create mode 100644 arch/riscv/mm/kasan_init.c
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-08-07 7:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 7:19 Nick Hu [this message]
2019-08-07 7:19 ` [PATCH 1/2] riscv: Add memmove string operation Nick Hu
2019-08-12 15:04 ` Christoph Hellwig
2019-08-13 23:50 ` Palmer Dabbelt
2019-08-14 2:22 ` Paul Walmsley
2019-08-14 3:27 ` Nick Hu
2019-08-14 17:03 ` Paul Walmsley
2019-08-15 3:12 ` Nick Hu
2019-08-15 18:27 ` Paul Walmsley
2019-08-19 6:29 ` Nick Hu
2019-08-14 18:33 ` Palmer Dabbelt
2019-08-22 15:59 ` Andrey Ryabinin
2019-08-27 9:07 ` Nick Hu
2019-08-27 9:33 ` Andrey Ryabinin
2019-08-28 3:06 ` Nick Hu
2019-08-07 7:19 ` [PATCH 2/2] riscv: Add KASAN support Nick Hu
2019-08-12 15:10 ` Christoph Hellwig
2019-08-14 7:44 ` Nick Hu
2019-08-22 17:08 ` Andrey Ryabinin
2019-09-03 15:08 ` Daniel Axtens
2019-09-04 2:24 ` 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.1565161957.git.nickhu@andestech.com \
--to=nickhu@andestech.com \
--cc=Anup.Patel@wdc.com \
--cc=alankao@andestech.com \
--cc=alexios.zavras@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=aryabinin@virtuozzo.com \
--cc=atish.patra@wdc.com \
--cc=deanbo422@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=green.hu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
--cc=zong@andestech.com \
/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).