Re: [PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-12-13 Thread Daniel Axtens
Hi Christophe, - We run a lot of code at boot in real mode. This includes stuff like printk(), so it's not feasible to just disable instrumentation around it. >>> >>> Have you definitely given up the idea of doing a standard implementation >>> of KASAN like other 64

Re: [PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-12-13 Thread Christophe Leroy
Le 10/12/2019 à 06:10, Daniel Axtens a écrit : Christophe Leroy writes: Le 07/08/2019 à 01:38, Daniel Axtens a écrit : KASAN support on powerpc64 is interesting: - We want to be able to support inline instrumentation so as to be able to catch global and stack issues. - We run

Re: [PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-12-09 Thread Daniel Axtens
Christophe Leroy writes: > Le 07/08/2019 à 01:38, Daniel Axtens a écrit : >> KASAN support on powerpc64 is interesting: >> >> - We want to be able to support inline instrumentation so as to be >> able to catch global and stack issues. >> >> - We run a lot of code at boot in real mode.

Re: [PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-08-09 Thread Christophe Leroy
Hi Daniel, Le 07/08/2019 à 18:34, Christophe Leroy a écrit : Le 07/08/2019 à 01:38, Daniel Axtens a écrit : KASAN support on powerpc64 is interesting:   - We want to be able to support inline instrumentation so as to be     able to catch global and stack issues.   - We run a lot of code at

Re: [PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-08-07 Thread Christophe Leroy
Le 07/08/2019 à 01:38, Daniel Axtens a écrit : KASAN support on powerpc64 is interesting: - We want to be able to support inline instrumentation so as to be able to catch global and stack issues. - We run a lot of code at boot in real mode. This includes stuff like printk(), so

[PATCH 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support

2019-08-06 Thread Daniel Axtens
KASAN support on powerpc64 is interesting: - We want to be able to support inline instrumentation so as to be able to catch global and stack issues. - We run a lot of code at boot in real mode. This includes stuff like printk(), so it's not feasible to just disable instrumentation