[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a060e08e-c119-0d37-d220-409b3d7539d3@c-s.fr>
Date: Mon, 17 Feb 2020 07:45:46 +0100
From: Christophe Leroy <christophe.leroy@....fr>
To: Michael Neuling <mikey@...ling.org>,
Daniel Axtens <dja@...ens.net>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
kasan-dev@...glegroups.com, aneesh.kumar@...ux.ibm.com,
bsingharora@...il.com
Subject: Re: [PATCH v7 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support
Le 17/02/2020 à 00:08, Michael Neuling a écrit :
> Daniel.
>
> Can you start this commit message with a simple description of what you are
> actually doing? This reads like you've been on a long journey to Mordor and
> back, which as a reader of this patch in the long distant future, I don't care
> about. I just want to know what you're implementing.
>
> Also I'm struggling to review this as I don't know what software or hardware
> mechanisms you are using to perform sanitisation.
KASAN is standard, it's simply using GCC ASAN in kernel mode, ie kernel
is built with -fsanitize=kernel-address
(https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html)
You have more details there:
https://www.kernel.org/doc/html/latest/dev-tools/kasan.html
Christophe
Powered by blists - more mailing lists