On Fri, May 22, 2020 at 4:02 AM Walter Wu <[email protected]> wrote: > > Generic KASAN will support to record the last two call_rcu() call stacks > and print them in KASAN report. So that need to update documentation.
Reviewed-and-tested-by: Dmitry Vyukov <[email protected]> > Signed-off-by: Walter Wu <[email protected]> > Cc: Andrey Ryabinin <[email protected]> > Cc: Dmitry Vyukov <[email protected]> > Cc: Alexander Potapenko <[email protected]> > Cc: Jonathan Corbet <[email protected]> > --- > Documentation/dev-tools/kasan.rst | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/dev-tools/kasan.rst > b/Documentation/dev-tools/kasan.rst > index c652d740735d..fede42e6536b 100644 > --- a/Documentation/dev-tools/kasan.rst > +++ b/Documentation/dev-tools/kasan.rst > @@ -193,6 +193,9 @@ function calls GCC directly inserts the code to check the > shadow memory. > This option significantly enlarges kernel but it gives x1.1-x2 performance > boost over outline instrumented kernel. > > +Generic KASAN prints up to 2 call_rcu() call stacks in reports, the last one > +and the second to last. > + > Software tag-based KASAN > ~~~~~~~~~~~~~~~~~~~~~~~~ > > -- > 2.18.0 > > -- > You received this message because you are subscribed to the Google Groups > "kasan-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/kasan-dev/20200522020212.23460-1-walter-zh.wu%40mediatek.com.
