mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-30 11:41:38 -04:00
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". [[email protected]: simplify & clenup code] Link: https://lkml.kernel.org/r/[email protected]] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Walter Wu <[email protected]> Signed-off-by: Andrey Ryabinin <[email protected]> Acked-by: Andrey Konovalov <[email protected]> Cc: Dmitry Vyukov <[email protected]> Cc: Alexander Potapenko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
This commit is contained in:
parent
c59180ae3e
commit
ae8f06b31a
5 changed files with 99 additions and 13 deletions
|
|
@ -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.
|
||||
|
||||
config KASAN_SW_TAGS_IDENTIFY
|
||||
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.
|
||||
|
||||
config TEST_KASAN
|
||||
tristate "Module for testing KASAN for bug detection"
|
||||
depends on m && KASAN
|
||||
|
|
|
|||
Loading…
Reference in a new issue