On Wed, 13 Apr 2016 13:20:09 +0200 Alexander Potapenko <glider@xxxxxxxxxx> wrote:
> Instead of calling kasan_krealloc(), which replaces the memory allocation
> stack ID (if stack depot is used), just unpoison the whole memory chunk.
I don't understand why these two patches exist. Bugfix? Cleanup?
Optimization?
I had to change kmalloc_tests_init() a bit due to
mm-kasan-initial-memory-quarantine-implementation.patch:
kasan_stack_oob();
kasan_global_oob();
#ifdef CONFIG_SLAB
kasan_quarantine_cache();
#endif
+ ksize_unpoisons_memory();
return -EAGAIN;
}
Please check.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>