Tao Zeng cfe5efa496 mm: fix too many wrong kasan report [1/1] ...

PD#SWPL-3583

Problem:
After merge change:
http://scgit.amlogic.com:8080/#/c/55018/
Too many wrong kasan report occur when booting kernel

Solution:
Fix kasan poison address range when free wasted memory.

Verify:
P212

Change-Id: I576a7edb7b4e70f9c6c782639f433ad45bafba1d
Signed-off-by: Tao Zeng <tao.zeng@amlogic.com>

2019-02-26 18:16:48 +09:00

..

kasan_init.c

x86/kasan, mm: Introduce generic kasan_populate_zero_shadow()

2015-08-22 14:54:55 +02:00

kasan.c

mm: fix too many wrong kasan report [1/1]

2019-02-26 18:16:48 +09:00

kasan.h

UPSTREAM: kasan: add functions for unpoisoning stack variables

2018-03-15 08:28:37 -07:00

Makefile

mm, kasan: switch SLUB to stackdepot, enable memory quarantine for SLUB

2016-07-28 16:07:41 -07:00

quarantine.c

UPSTREAM: kasan: fix races in quarantine_remove_cache()

2017-12-18 15:07:47 -08:00

report.c

UPSTREAM: kasan: support alloca() poisoning

2018-03-15 08:28:37 -07:00