Le 18/05/2022 à 12:07, Paul Mackerras a écrit : > From: Daniel Axtens <d...@axtens.net> > > Signed-off-by: Paul Mackerras <pau...@ozlabs.org>
This change doesn't apply, can you rebase ? Thanks Christophe > --- > Documentation/dev-tools/kasan.rst | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/Documentation/dev-tools/kasan.rst > b/Documentation/dev-tools/kasan.rst > index 8089c559d339..448995c11bee 100644 > --- a/Documentation/dev-tools/kasan.rst > +++ b/Documentation/dev-tools/kasan.rst > @@ -36,7 +36,9 @@ Both software KASAN modes work with SLUB and SLAB memory > allocators, > while the hardware tag-based KASAN currently only supports SLUB. > > Currently, generic KASAN is supported for the x86_64, arm, arm64, xtensa, > s390, > -and riscv architectures, and tag-based KASAN modes are supported only for > arm64. > +and riscv architectures. It is also supported on powerpc for 32-bit kernels > and > +for 64-bit kernels running under the Radix MMU. Tag-based KASAN modes are > +supported only for arm64. > > Usage > ----- > @@ -351,6 +353,9 @@ With ``CONFIG_KASAN_VMALLOC``, KASAN can cover vmalloc > space at the > cost of greater memory usage. Currently, this is supported on x86, > riscv, s390, and powerpc. > > +It is optional, except on 64-bit powerpc kernels, and on 32-bit > +powerpc kernels with module support, where it is required. > + > This works by hooking into vmalloc and vmap and dynamically > allocating real shadow memory to back the mappings. >
