From: Nick Hu <nickhu@andestech.com> To: <aryabinin@virtuozzo.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> Cc: Nick Hu <nickhu@andestech.com> Subject: [PATCH v4 0/3] KASAN support for RISC-V Date: Mon, 28 Oct 2019 10:40:58 +0800 [thread overview] Message-ID: <20191028024101.26655-1-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. Changes in v4: - Correct the commit log - Fix the bug reported by Greentime Hu Nick Hu (3): kasan: No KASAN's memmove check if archs don't have 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: <aryabinin@virtuozzo.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> Cc: Nick Hu <nickhu@andestech.com> Subject: [PATCH v4 0/3] KASAN support for RISC-V Date: Mon, 28 Oct 2019 10:40:58 +0800 [thread overview] Message-ID: <20191028024101.26655-1-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. Changes in v4: - Correct the commit log - Fix the bug reported by Greentime Hu Nick Hu (3): kasan: No KASAN's memmove check if archs don't have 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-28 2:42 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-28 2:40 Nick Hu [this message] 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-10-28 2:40 ` Nick Hu 2019-11-17 4:57 ` Paul Walmsley 2019-11-17 4:57 ` Paul Walmsley 2019-11-17 4:57 ` Paul Walmsley 2019-11-18 8:41 ` Dmitry Vyukov 2019-11-18 8:41 ` Dmitry Vyukov 2019-11-18 8:41 ` Dmitry Vyukov 2019-11-18 16:22 ` Andrey Ryabinin 2019-11-18 16:22 ` Andrey Ryabinin 2019-10-28 2:41 ` [PATCH v4 2/3] riscv: Add KASAN support Nick Hu 2019-10-28 2:41 ` Nick Hu 2019-10-28 2:41 ` [PATCH v4 3/3] kasan: Add riscv to KASAN documentation Nick Hu 2019-10-28 2:41 ` Nick Hu 2019-10-28 7:01 ` [PATCH v4 0/3] KASAN support for RISC-V Greentime Hu 2019-10-28 7:01 ` Greentime Hu 2019-10-28 7:01 ` 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=20191028024101.26655-1-nickhu@andestech.com \ --to=nickhu@andestech.com \ --cc=Anup.Patel@wdc.com \ --cc=alankao@andestech.com \ --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=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=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: linkBe 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.