Generic KASAN also supports to record the last two timer and workqueue stacks and print them in KASAN report. So that need to update documentation.
Signed-off-by: Walter Wu <walter-zh...@mediatek.com> Suggested-by: Marco Elver <el...@google.com> Acked-by: Marco Elver <el...@google.com> Reviewed-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> --- v3: - Thanks for Marco suggestion --- Documentation/dev-tools/kasan.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst index 38fd5681fade..698ccb65e634 100644 --- a/Documentation/dev-tools/kasan.rst +++ b/Documentation/dev-tools/kasan.rst @@ -190,8 +190,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. +Generic KASAN also reports the last 2 call stacks to creation of work that +potentially has access to an object. Call stacks for the following are shown: +call_rcu(), timer and workqueue queuing. Software tag-based KASAN ~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.18.0
