From: Daniel Axtens <dja@axtens.net>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, elver@google.com,
akpm@linux-foundation.org, andreyknvl@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, christophe.leroy@csgroup.eu,
aneesh.kumar@linux.ibm.com, bsingharora@gmail.com,
Daniel Axtens <dja@axtens.net>
Subject: [PATCH v13 0/3] KASAN core changes for ppc64 radix KASAN
Date: Wed, 16 Jun 2021 18:02:41 +1000 [thread overview]
Message-ID: <20210616080244.51236-1-dja@axtens.net> (raw)
Building on the work of Christophe, Aneesh and Balbir, I've ported
KASAN to 64-bit Book3S kernels running on the Radix MMU. I've been
trying this for a while, but we keep having collisions between the
kasan code in the mm tree and the code I want to put in to the ppc
tree.
So this series just contains the kasan core changes that we
need. These can go in via the mm tree. I will then propose the powerpc
changes for a later cycle. (The most recent RFC for the powerpc
changes is in the last series at
https://lore.kernel.org/linux-mm/20210615014705.2234866-1-dja@axtens.net/
)
v13 applies to next-20210611. There should be no noticeable changes to
other platforms.
Changes since v12: respond to Marco's review comments - clean up the
help for ARCH_DISABLE_KASAN_INLINE, and add an arch readiness check to
the new granule poisioning function. Thanks Marco.
Kind regards,
Daniel
Daniel Axtens (3):
kasan: allow an architecture to disable inline instrumentation
kasan: allow architectures to provide an outline readiness check
kasan: define and use MAX_PTRS_PER_* for early shadow tables
include/linux/kasan.h | 18 +++++++++++++++---
lib/Kconfig.kasan | 14 ++++++++++++++
mm/kasan/common.c | 4 ++++
mm/kasan/generic.c | 3 +++
mm/kasan/init.c | 6 +++---
mm/kasan/kasan.h | 4 ++++
mm/kasan/shadow.c | 8 ++++++++
7 files changed, 51 insertions(+), 6 deletions(-)
--
2.30.2
next reply other threads:[~2021-06-16 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:02 Daniel Axtens [this message]
2021-06-16 8:02 ` [PATCH v13 1/3] kasan: allow an architecture to disable inline instrumentation Daniel Axtens
2021-06-16 9:09 ` Marco Elver
2021-06-16 8:02 ` [PATCH v13 2/3] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2021-06-16 8:56 ` Marco Elver
2021-06-16 8:02 ` [PATCH v13 3/3] kasan: define and use MAX_PTRS_PER_* for early shadow tables Daniel Axtens
2021-06-16 9:07 ` Marco Elver
2021-06-16 17:23 ` Christophe Leroy
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=20210616080244.51236-1-dja@axtens.net \
--to=dja@axtens.net \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).