[lkml]   [2020]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH v4 6/6] kasan: update documentation for generic kasan
Generic KASAN also supports to record the last two timer and workqueue
stacks and print them in KASAN report. So that need to update

Signed-off-by: Walter Wu <>
Suggested-by: Marco Elver <>
Acked-by: Marco Elver <>
Reviewed-by: Dmitry Vyukov <>
Reviewed-by: Andrey Konovalov <>
Cc: Andrey Ryabinin <>
Cc: Alexander Potapenko <>
Cc: Jonathan Corbet <>

- 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
 \ /
  Last update: 2020-09-24 06:13    [W:0.049 / U:2.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site