diff options
| author | Andrey Ryabinin <aryabinin@virtuozzo.com> | 2019-12-17 20:51:38 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-12-17 20:59:59 -0800 |
| commit | d98c9e83b5e7ca78175df1b13ac4a6d460d3962d (patch) | |
| tree | d978ad6db67a7bc39ac92ef36e8b22b06a4e13eb /mm/memory.c | |
| parent | 2187f215ebaac73ddbd814696d7c7fa34f0c3de0 (diff) | |
| download | linux-d98c9e83b5e7ca78175df1b13ac4a6d460d3962d.tar.gz linux-d98c9e83b5e7ca78175df1b13ac4a6d460d3962d.tar.bz2 linux-d98c9e83b5e7ca78175df1b13ac4a6d460d3962d.zip | |
kasan: fix crashes on access to memory mapped by vm_map_ram()
With CONFIG_KASAN_VMALLOC=y any use of memory obtained via vm_map_ram()
will crash because there is no shadow backing that memory.
Instead of sprinkling additional kasan_populate_vmalloc() calls all over
the vmalloc code, move it into alloc_vmap_area(). This will fix
vm_map_ram() and simplify the code a bit.
[aryabinin@virtuozzo.com: v2]
Link: http://lkml.kernel.org/r/20191205095942.1761-1-aryabinin@virtuozzo.comLink: http://lkml.kernel.org/r/20191204204534.32202-1-aryabinin@virtuozzo.com
Fixes: 3c5c3cfb9ef4 ("kasan: support backing vmalloc space with real shadow memory")
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Cc: Daniel Axtens <dja@axtens.net>
Cc: Alexander Potapenko <glider@google.com>
Cc: Daniel Axtens <dja@axtens.net>
Cc: Qian Cai <cai@lca.pw>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions