summaryrefslogtreecommitdiffstats
path: root/Documentation/dev-tools/kasan.rst
diff options
context:
space:
mode:
authorMike Rapoport <rppt@linux.vnet.ibm.com>2018-03-21 15:22:47 -0400
committerJonathan Corbet <corbet@lwn.net>2018-04-16 16:18:15 -0400
commitad56b738c5dd223a2f66685830f82194025a6138 (patch)
tree3994f40f1f93aec279d0b5c9117c0085a9f9ab03 /Documentation/dev-tools/kasan.rst
parent3406bb5c64a091ad887c3fb339ad88e9e88ef938 (diff)
docs/vm: rename documentation files to .rst
Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/dev-tools/kasan.rst')
-rw-r--r--Documentation/dev-tools/kasan.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst
index f7a18f274357..aabc8738b3d8 100644
--- a/Documentation/dev-tools/kasan.rst
+++ b/Documentation/dev-tools/kasan.rst
@@ -120,7 +120,7 @@ A typical out of bounds access report looks like this::
120 120
121The header of the report discribe what kind of bug happened and what kind of 121The header of the report discribe what kind of bug happened and what kind of
122access caused it. It's followed by the description of the accessed slub object 122access caused it. It's followed by the description of the accessed slub object
123(see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and 123(see 'SLUB Debug output' section in Documentation/vm/slub.rst for details) and
124the description of the accessed memory page. 124the description of the accessed memory page.
125 125
126In the last section the report shows memory state around the accessed address. 126In the last section the report shows memory state around the accessed address.