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.
Signed-off-by: Walter Wu <walter-zh...@mediatek.com> Reviewed-and-tested-by: Dmitry Vyukov <dvyu...@google.com> Reviewed-by: Andrey Konovalov <andreyk...@google.com> Cc: Andrey Ryabinin <aryabi...@virtuozzo.com> Cc: Alexander Potapenko <gli...@google.com> Cc: Jonathan Corbet <cor...@lwn.net> --- 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
