[PATCH v5 4/4] kasan: update documentation for generic kasan

Walter Wu walter-zh.wu at mediatek.com
Wed Dec 2 21:30:37 EST 2020

Generic KASAN also supports to record the last two workqueue
stacks and print them in KASAN report. So that need to update

Signed-off-by: Walter Wu <walter-zh.wu at mediatek.com>
Suggested-by: Marco Elver <elver at google.com>
Acked-by: Marco Elver <elver at google.com>
Reviewed-by: Dmitry Vyukov <dvyukov at google.com>
Reviewed-by: Andrey Konovalov <andreyknvl at google.com>
Cc: Andrey Ryabinin <aryabinin at virtuozzo.com>
Cc: Alexander Potapenko <glider at google.com>
Cc: Jonathan Corbet <corbet at lwn.net>

- remove timer stack description

- 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 c09c9ca2ff1c..3cb556ceb4a5 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() and workqueue queuing.
 Software tag-based KASAN

More information about the linux-arm-kernel mailing list