Re: [PATCH] kdb: use memmove instead of overlapping memcpy

On 02/02/2018 08:59 AM, Arnd Bergmann wrote: 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

Re: [PATCH] kdb: use memmove instead of overlapping memcpy

On 02/02/2018 08:59 AM, Arnd Bergmann wrote: 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