linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Paul Mackerras <paulus@ozlabs.org>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/3] KASAN support for 64-bit Book 3S powerpc
Date: Sun, 15 May 2022 07:59:03 +0000	[thread overview]
Message-ID: <cc26b703-c9e7-ec58-de6c-8feb3fd37947@csgroup.eu> (raw)
In-Reply-To: <Yntk7oERGce44+Sd@cleo>



Le 11/05/2022 à 09:25, Paul Mackerras a écrit :
> [Vous ne recevez pas souvent de courriers de la part de paulus@ozlabs.org. D?couvrez pourquoi cela peut ?tre important ? l'adresse https://aka.ms/LearnAboutSenderIdentification.]
> 
> This patch series implements KASAN on 64-bit POWER with radix MMU,
> such as POWER9 or POWER10.  Daniel Axtens posted previous versions of
> these patches, but is no longer working on KASAN, and I have been
> asked to get them ready for inclusion.
> 
> Because of various technical difficulties, mostly around the need to
> allow for code that runs in real mode, we only support "outline" mode
> (as opposed to "inline" mode), where the compiler adds a call to
> a checking procedure before every store to memory.
> 
> The main patch is still marked [RFC] because of known deficiencies,
> specifically that the kernel will crash on boot on a HPT system, and
> that out-of-bounds accesses to module global data are not caught
> (which leads to one of the KASAN tests failing).
> 
> Comments welcome.  I may not have addressed all the comments about
> previous versions of these patches; if so, then please just repeat
> your comments.

Last patch is quite big. I think it would be worth splitting in several 
patches. A made a few suggestions while reviewing it. I think it could 
also be worth putting all the adding of no_instr and KASAN_SANITIZE := n 
in a preparatory patch.

Also, your last patch includes v1 of "powerpc: make stack walking 
KASAN-safe" 
(https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20210528074806.1311297-1-dja@axtens.net/) 
while v2 was merged 
(https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20210614120907.1952321-1-dja@axtens.net/)

Christophe

      parent reply	other threads:[~2022-05-15  7:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  7:25 [PATCH 0/3] KASAN support for 64-bit Book 3S powerpc Paul Mackerras
2022-05-11  7:26 ` [PATCH 1/3] kasan: Document support on 32-bit powerpc Paul Mackerras
2022-05-11  7:27 ` [PATCH 2/3] powerpc/mm/kasan: rename kasan_init_32.c to init_32.c Paul Mackerras
2022-05-11  7:28 ` [PATCH 3/3] [RFC] powerpc: Book3S 64-bit outline-only KASAN support Paul Mackerras
2022-05-15  7:33   ` Christophe Leroy
2022-05-17  7:31     ` Paul Mackerras
2022-05-17  8:06       ` Christophe Leroy
2022-05-15  7:59 ` Christophe Leroy [this message]

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=cc26b703-c9e7-ec58-de6c-8feb3fd37947@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@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).