diff options
| author | Andrey Ryabinin <aryabinin@virtuozzo.com> | 2016-05-20 16:59:20 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-20 17:58:30 -0700 |
| commit | 936bb4bbbb832f81055328b84e5afe1fc7246a8d (patch) | |
| tree | f61b89546b9403246b7d0eebc7f87e41d54860ce /mm/zsmalloc.c | |
| parent | 96fe805fb6fe9b2ed12fc54ad0e3e6829a4152cb (diff) | |
| download | linux-936bb4bbbb832f81055328b84e5afe1fc7246a8d.tar.gz linux-936bb4bbbb832f81055328b84e5afe1fc7246a8d.tar.bz2 linux-936bb4bbbb832f81055328b84e5afe1fc7246a8d.zip | |
mm/kasan: print name of mem[set,cpy,move]() caller in report
When bogus memory access happens in mem[set,cpy,move]() it's usually
caller's fault. So don't blame mem[set,cpy,move]() in bug report, blame
the caller instead.
Before:
BUG: KASAN: out-of-bounds access in memset+0x23/0x40 at <address>
After:
BUG: KASAN: out-of-bounds access in <memset_caller> at <address>
Link: http://lkml.kernel.org/r/1462538722-1574-2-git-send-email-aryabinin@virtuozzo.com
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Acked-by: Alexander Potapenko <glider@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/zsmalloc.c')
0 files changed, 0 insertions, 0 deletions