From: Marco Elver <elver@google.com> To: Daniel Axtens <dja@axtens.net> Cc: LKML <linux-kernel@vger.kernel.org>, Linux Memory Management List <linux-mm@kvack.org>, linuxppc-dev@lists.ozlabs.org, kasan-dev <kasan-dev@googlegroups.com>, Christophe Leroy <christophe.leroy@csgroup.eu>, aneesh.kumar@linux.ibm.com, Balbir Singh <bsingharora@gmail.com>, Andrey Konovalov <andreyknvl@gmail.com> Subject: Re: [PATCH v12 0/6] KASAN core changes for ppc64 radix KASAN Date: Tue, 15 Jun 2021 12:31:02 +0200 [thread overview] Message-ID: <CANpmjNO9EdwPEiNPu630a2kgsxMXYiNU_phKH2=7Z5YFRCSR1A@mail.gmail.com> (raw) In-Reply-To: <20210615014705.2234866-1-dja@axtens.net> [+Cc Andrey] On Tue, 15 Jun 2021 at 03:47, Daniel Axtens <dja@axtens.net> wrote: > > 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 my aim here is for patches 1 through 4 or 1 through 5 > to go in via the mm tree. I think this is reasonable. I'd suggest just sending non-ppc patches separately (i.e. split the series explicitly) to KASAN maintainers, and ensure to Cc Andrew, too. Just point at this series to illustrate how it'll be used. I think the patches are fine, but I'm not entirely sure about the current placements of kasan_arch_is_ready(), so hopefully Andrey can also have a look. > I will then propose the powerpc changes for > a later cycle. (I have attached them to this series as an RFC, and > there are still outstanding review comments I need to attend to.) > > v12 applies to next-20210611. There should be no noticable changes to > other platforms. > > Kind regards, > Daniel > > Daniel Axtens (6): > 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 ^^ Up to here could be a separate series to go through -mm. > kasan: Document support on 32-bit powerpc ^^ The Documentation changes are minimal and not just confined to kasan.rst it seems. In fact your "powerpc: Book3S .." patch changes Documentation more. So you could just take "kasan: Document support on 32-bit powerpc" through ppc tree as well. > powerpc/mm/kasan: rename kasan_init_32.c to init_32.c > [RFC] powerpc: Book3S 64-bit outline-only KASAN support
WARNING: multiple messages have this Message-ID (diff)
From: Marco Elver <elver@google.com> To: Daniel Axtens <dja@axtens.net> Cc: aneesh.kumar@linux.ibm.com, LKML <linux-kernel@vger.kernel.org>, Linux Memory Management List <linux-mm@kvack.org>, kasan-dev <kasan-dev@googlegroups.com>, linuxppc-dev@lists.ozlabs.org, Andrey Konovalov <andreyknvl@gmail.com> Subject: Re: [PATCH v12 0/6] KASAN core changes for ppc64 radix KASAN Date: Tue, 15 Jun 2021 12:31:02 +0200 [thread overview] Message-ID: <CANpmjNO9EdwPEiNPu630a2kgsxMXYiNU_phKH2=7Z5YFRCSR1A@mail.gmail.com> (raw) In-Reply-To: <20210615014705.2234866-1-dja@axtens.net> [+Cc Andrey] On Tue, 15 Jun 2021 at 03:47, Daniel Axtens <dja@axtens.net> wrote: > > 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 my aim here is for patches 1 through 4 or 1 through 5 > to go in via the mm tree. I think this is reasonable. I'd suggest just sending non-ppc patches separately (i.e. split the series explicitly) to KASAN maintainers, and ensure to Cc Andrew, too. Just point at this series to illustrate how it'll be used. I think the patches are fine, but I'm not entirely sure about the current placements of kasan_arch_is_ready(), so hopefully Andrey can also have a look. > I will then propose the powerpc changes for > a later cycle. (I have attached them to this series as an RFC, and > there are still outstanding review comments I need to attend to.) > > v12 applies to next-20210611. There should be no noticable changes to > other platforms. > > Kind regards, > Daniel > > Daniel Axtens (6): > 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 ^^ Up to here could be a separate series to go through -mm. > kasan: Document support on 32-bit powerpc ^^ The Documentation changes are minimal and not just confined to kasan.rst it seems. In fact your "powerpc: Book3S .." patch changes Documentation more. So you could just take "kasan: Document support on 32-bit powerpc" through ppc tree as well. > powerpc/mm/kasan: rename kasan_init_32.c to init_32.c > [RFC] powerpc: Book3S 64-bit outline-only KASAN support
next prev parent reply other threads:[~2021-06-15 10:31 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-15 1:46 [PATCH v12 0/6] KASAN core changes for ppc64 radix KASAN Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 1/6] kasan: allow an architecture to disable inline instrumentation Daniel Axtens 2021-06-15 7:46 ` Marco Elver 2021-06-15 7:46 ` Marco Elver 2021-06-15 7:46 ` Marco Elver 2021-06-16 4:39 ` Daniel Axtens 2021-06-16 4:39 ` Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 2/6] kasan: allow architectures to provide an outline readiness check Daniel Axtens 2021-06-15 1:47 ` Daniel Axtens 2021-06-15 10:08 ` Marco Elver 2021-06-15 10:08 ` Marco Elver 2021-06-15 10:08 ` Marco Elver 2021-06-16 4:41 ` Daniel Axtens 2021-06-16 4:41 ` Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 3/6] kasan: define and use MAX_PTRS_PER_* for early shadow tables Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 4/6] kasan: Document support on 32-bit powerpc Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 5/6] powerpc/mm/kasan: rename kasan_init_32.c to init_32.c Daniel Axtens 2021-06-15 1:47 ` [PATCH v12 6/6] [RFC] powerpc: Book3S 64-bit outline-only KASAN support Daniel Axtens 2021-06-15 10:31 ` Marco Elver [this message] 2021-06-15 10:31 ` [PATCH v12 0/6] KASAN core changes for ppc64 radix KASAN Marco Elver 2021-06-15 10:31 ` Marco Elver
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='CANpmjNO9EdwPEiNPu630a2kgsxMXYiNU_phKH2=7Z5YFRCSR1A@mail.gmail.com' \ --to=elver@google.com \ --cc=andreyknvl@gmail.com \ --cc=aneesh.kumar@linux.ibm.com \ --cc=bsingharora@gmail.com \ --cc=christophe.leroy@csgroup.eu \ --cc=dja@axtens.net \ --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: 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.