From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Daniel Axtens <dja@axtens.net>,
aneesh.kumar@linux.ibm.com, christophe.leroy@c-s.fr,
bsingharora@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, kasan-dev@googlegroups.com
Subject: Re: [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory
Date: Fri, 15 Feb 2019 11:24:01 +1100 [thread overview]
Message-ID: <74ca7b47-b8f8-0535-a2a5-dafc51a28649@au1.ibm.com> (raw)
In-Reply-To: <20190215000441.14323-5-dja@axtens.net>
On 15/2/19 11:04 am, Daniel Axtens wrote:
> In preparation for adding ppc64 implementations, break out the
> code into its own subdirectory.
>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
If Christophe respins his series, can we squash this in there?
> ---
> arch/powerpc/mm/Makefile | 4 +---
> arch/powerpc/mm/kasan/Makefile | 5 +++++
> arch/powerpc/mm/{kasan_init.c => kasan/kasan_init_32.c} | 0
> 3 files changed, 6 insertions(+), 3 deletions(-)
> create mode 100644 arch/powerpc/mm/kasan/Makefile
> rename arch/powerpc/mm/{kasan_init.c => kasan/kasan_init_32.c} (100%)
>
> diff --git a/arch/powerpc/mm/Makefile b/arch/powerpc/mm/Makefile
> index d6b76f25f6de..457c0ea2b5e7 100644
> --- a/arch/powerpc/mm/Makefile
> +++ b/arch/powerpc/mm/Makefile
> @@ -7,8 +7,6 @@ ccflags-$(CONFIG_PPC64) := $(NO_MINIMAL_TOC)
>
> CFLAGS_REMOVE_slb.o = $(CC_FLAGS_FTRACE)
>
> -KASAN_SANITIZE_kasan_init.o := n
> -
> obj-y := fault.o mem.o pgtable.o mmap.o \
> init_$(BITS).o pgtable_$(BITS).o \
> init-common.o mmu_context.o drmem.o
> @@ -57,4 +55,4 @@ obj-$(CONFIG_PPC_BOOK3S_64) += dump_linuxpagetables-book3s64.o
> endif
> obj-$(CONFIG_PPC_HTDUMP) += dump_hashpagetable.o
> obj-$(CONFIG_PPC_MEM_KEYS) += pkeys.o
> -obj-$(CONFIG_KASAN) += kasan_init.o
> +obj-$(CONFIG_KASAN) += kasan/
> diff --git a/arch/powerpc/mm/kasan/Makefile b/arch/powerpc/mm/kasan/Makefile
> new file mode 100644
> index 000000000000..6577897673dd
> --- /dev/null
> +++ b/arch/powerpc/mm/kasan/Makefile
> @@ -0,0 +1,5 @@
> +# SPDX-License-Identifier: GPL-2.0
> +
> +KASAN_SANITIZE := n
> +
> +obj-$(CONFIG_PPC32) += kasan_init_32.o
> diff --git a/arch/powerpc/mm/kasan_init.c b/arch/powerpc/mm/kasan/kasan_init_32.c
> similarity index 100%
> rename from arch/powerpc/mm/kasan_init.c
> rename to arch/powerpc/mm/kasan/kasan_init_32.c
>
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2019-02-15 0:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:04 [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 1/5] kasan: do not open-code addr_has_shadow Daniel Axtens
2019-02-15 0:12 ` Andrew Donnellan
2019-02-15 8:21 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 2/5] kasan: allow architectures to manage the memory-to-shadow mapping Daniel Axtens
2019-02-15 6:35 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 3/5] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2019-02-15 8:25 ` Dmitry Vyukov
2019-02-17 12:05 ` christophe leroy
2019-02-18 6:13 ` Daniel Axtens
2019-02-25 14:01 ` Christophe Leroy
2019-02-26 0:14 ` Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory Daniel Axtens
2019-02-15 0:24 ` Andrew Donnellan [this message]
2019-02-17 16:29 ` christophe leroy
2019-02-18 9:14 ` Michael Ellerman
2019-02-18 12:27 ` Christophe Leroy
2019-02-19 0:44 ` Michael Ellerman
2019-02-15 0:04 ` [RFC PATCH 5/5] powerpc: KASAN for 64bit Book3E Daniel Axtens
2019-02-15 8:28 ` Dmitry Vyukov
2019-02-19 6:37 ` Daniel Axtens
2019-02-17 14:06 ` christophe leroy
2019-02-18 19:26 ` Christophe Leroy
2019-02-19 0:14 ` Daniel Axtens
2019-02-15 16:39 ` [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Christophe Leroy
2019-02-17 6:34 ` Balbir Singh
2019-02-19 6:35 ` 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=74ca7b47-b8f8-0535-a2a5-dafc51a28649@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=dja@axtens.net \
--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;
as well as URLs for NNTP newsgroup(s).