Arnd Bergmann 184adf40d1 kdb: use memmove instead of overlapping memcpy ...

commit 2cf2f0d5b9 upstream.

gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so
we should really use memmove(), which is defined to handle that correctly:

In function 'memcpy',
    inlined from 'kdbnearsym' at /git/arm-soc/kernel/debug/kdb/kdb_support.c:132:4:
/git/arm-soc/include/linux/string.h:353:9: error: '__builtin_memcpy' accessing 792 bytes at offsets 0 and 8 overlaps 784 bytes at offset 8 [-Werror=restrict]
  return __builtin_memcpy(p, q, size);

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

2018-12-08 13:03:36 +01:00

..

kdb

kdb: use memmove instead of overlapping memcpy

2018-12-08 13:03:36 +01:00

debug_core.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/nmi.h>

2017-03-02 08:42:30 +01:00

debug_core.h

kgdb/kdb: Fix no KDB config problem

2014-01-25 08:55:09 +01:00

gdbstub.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/signal.h>

2017-03-02 08:42:29 +01:00

Makefile

kdb: core for kgdb back end (1 of 2)

2010-05-20 21:04:20 -05:00