From: Daniel Axtens <dja@axtens.net>
To: aneesh.kumar@linux.ibm.com, christophe.leroy@c-s.fr,
bsingharora@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, kasan-dev@googlegroups.com,
Daniel Axtens <dja@axtens.net>
Subject: [RFC PATCH 0/7] powerpc: KASAN for 64-bit 3s radix
Date: Thu, 23 May 2019 15:21:13 +1000 [thread overview]
Message-ID: <20190523052120.18459-1-dja@axtens.net> (raw)
Building on the work of Christophe, Aneesh and Balbir, I've ported
KASAN to Book3S radix.
It builds on top Christophe's work on 32bit, and includes my work for
64-bit Book3E (3S doesn't really depend on 3E, but it was handy to
have around when developing and debugging).
This provides full inline instrumentation on radix, but does require
that you be able to specify the amount of memory on the system at
compile time. More details in patch 7.
Regards,
Daniel
Daniel Axtens (7):
kasan: do not open-code addr_has_shadow
kasan: allow architectures to manage the memory-to-shadow mapping
kasan: allow architectures to provide an outline readiness check
powerpc: KASAN for 64bit Book3E
kasan: allow arches to provide their own early shadow setup
kasan: allow arches to hook into global registration
powerpc: Book3S 64-bit "heavyweight" KASAN support
arch/powerpc/Kconfig | 2 +
arch/powerpc/Kconfig.debug | 17 ++-
arch/powerpc/Makefile | 7 ++
arch/powerpc/include/asm/kasan.h | 116 +++++++++++++++++++
arch/powerpc/kernel/prom.c | 40 +++++++
arch/powerpc/mm/kasan/Makefile | 2 +
arch/powerpc/mm/kasan/kasan_init_book3e_64.c | 50 ++++++++
arch/powerpc/mm/kasan/kasan_init_book3s_64.c | 67 +++++++++++
arch/powerpc/mm/nohash/Makefile | 5 +
include/linux/kasan.h | 13 +++
mm/kasan/generic.c | 9 +-
mm/kasan/generic_report.c | 2 +-
mm/kasan/init.c | 10 ++
mm/kasan/kasan.h | 6 +-
mm/kasan/report.c | 6 +-
mm/kasan/tags.c | 3 +-
16 files changed, 345 insertions(+), 10 deletions(-)
create mode 100644 arch/powerpc/mm/kasan/kasan_init_book3e_64.c
create mode 100644 arch/powerpc/mm/kasan/kasan_init_book3s_64.c
--
2.19.1
next reply other threads:[~2019-05-23 5:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 5:21 Daniel Axtens [this message]
2019-05-23 5:21 ` [RFC PATCH 1/7] kasan: do not open-code addr_has_shadow Daniel Axtens
2019-05-23 5:21 ` [RFC PATCH 2/7] kasan: allow architectures to manage the memory-to-shadow mapping Daniel Axtens
2019-05-23 5:21 ` [RFC PATCH 3/7] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2019-05-23 6:14 ` Christophe Leroy
2019-05-23 5:21 ` [RFC PATCH 4/7] powerpc: KASAN for 64bit Book3E Daniel Axtens
2019-05-23 6:15 ` Christophe Leroy
2019-05-23 5:21 ` [RFC PATCH 5/7] kasan: allow arches to provide their own early shadow setup Daniel Axtens
2019-05-23 5:21 ` [RFC PATCH 6/7] kasan: allow arches to hook into global registration Daniel Axtens
2019-05-23 6:31 ` Christophe Leroy
2019-05-23 6:59 ` Daniel Axtens
2019-05-23 5:21 ` [RFC PATCH 7/7] powerpc: Book3S 64-bit "heavyweight" KASAN support Daniel Axtens
2019-05-23 6:10 ` [RFC PATCH 0/7] powerpc: KASAN for 64-bit 3s radix Christophe Leroy
2019-05-23 6:18 ` Daniel Axtens
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=20190523052120.18459-1-dja@axtens.net \
--to=dja@axtens.net \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=kasan-dev@googlegroups.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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