aboutsummaryrefslogtreecommitdiffstats
path: root/lib/strncpy_from_user.c
diff options
context:
space:
mode:
authorAndrey Ryabinin <[email protected]>2016-05-20 23:59:20 +0000
committerLinus Torvalds <[email protected]>2016-05-21 00:58:30 +0000
commit936bb4bbbb832f81055328b84e5afe1fc7246a8d (patch)
treef61b89546b9403246b7d0eebc7f87e41d54860ce /lib/strncpy_from_user.c
parentmm, kasan: add a ksize() test (diff)
downloadkernel-936bb4bbbb832f81055328b84e5afe1fc7246a8d.tar.gz
kernel-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/[email protected] Signed-off-by: Andrey Ryabinin <[email protected]> Acked-by: Alexander Potapenko <[email protected]> Cc: Dmitry Vyukov <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: "H. Peter Anvin" <[email protected]> Cc: Thomas Gleixner <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'lib/strncpy_from_user.c')
0 files changed, 0 insertions, 0 deletions