path: root/lib/Kconfig.kasan
diff options
authorWalter Wu <>2019-09-23 15:34:13 -0700
committerLinus Torvalds <>2019-09-24 15:54:07 -0700
commitae8f06b31a83e54777514308a63f669a1fed519e (patch)
tree2963246f28ec918cfa7b5d75742eda07cf8deb62 /lib/Kconfig.kasan
parentc59180ae3e5b43d3534748b19a57905712ea5fff (diff)
kasan: add memory corruption identification for software tag-based mode
Add memory corruption identification at bug report for software tag-based mode. The report shows whether it is "use-after-free" or "out-of-bound" error instead of "invalid-access" error. This will make it easier for programmers to see the memory corruption problem. We extend the slab to store five old free pointer tag and free backtrace, we can check if the tagged address is in the slab record and make a good guess if the object is more like "use-after-free" or "out-of-bound". therefore every slab memory corruption can be identified whether it's "use-after-free" or "out-of-bound". [ simplify & clenup code] Link:] Link: Signed-off-by: Walter Wu <> Signed-off-by: Andrey Ryabinin <> Acked-by: Andrey Konovalov <> Cc: Dmitry Vyukov <> Cc: Alexander Potapenko <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'lib/Kconfig.kasan')
1 files changed, 8 insertions, 0 deletions
diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
index 7fa97a8b5717..6c9682ce0254 100644
--- a/lib/Kconfig.kasan
+++ b/lib/Kconfig.kasan
@@ -134,6 +134,14 @@ config KASAN_S390_4_LEVEL_PAGING
to 3TB of RAM with KASan enabled). This options allows to force
4-level paging instead.
+ bool "Enable memory corruption identification"
+ depends on KASAN_SW_TAGS
+ help
+ This option enables best-effort identification of bug type
+ (use-after-free or out-of-bounds) at the cost of increased
+ memory consumption.
tristate "Module for testing KASAN for bug detection"
depends on m && KASAN