Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Kees Cook
On Fri, Apr 22, 2016 at 12:49 AM, Ingo Molnar wrote: > > * Kees Cook wrote: > >> Two uses of memcpy (screen scrolling and ELF parsing) were handling >> overlapping memory areas. While there were no explicitly noticed bugs >> here (yet), it is best to fix

Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Kees Cook
On Fri, Apr 22, 2016 at 12:49 AM, Ingo Molnar wrote: > > * Kees Cook wrote: > >> Two uses of memcpy (screen scrolling and ELF parsing) were handling >> overlapping memory areas. While there were no explicitly noticed bugs >> here (yet), it is best to fix this so that the copying will always be

Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Ingo Molnar
* Kees Cook wrote: > Two uses of memcpy (screen scrolling and ELF parsing) were handling > overlapping memory areas. While there were no explicitly noticed bugs > here (yet), it is best to fix this so that the copying will always be > safe. > > Instead of making a new

Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Ingo Molnar
* Kees Cook wrote: > Two uses of memcpy (screen scrolling and ELF parsing) were handling > overlapping memory areas. While there were no explicitly noticed bugs > here (yet), it is best to fix this so that the copying will always be > safe. > > Instead of making a new memmove function that

Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Ingo Molnar
* Kees Cook wrote: > Two uses of memcpy (screen scrolling and ELF parsing) were handling > overlapping memory areas. While there were no explicitly noticed bugs > here (yet), it is best to fix this so that the copying will always be > safe. > > Instead of making a new

Re: [PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-22 Thread Ingo Molnar
* Kees Cook wrote: > Two uses of memcpy (screen scrolling and ELF parsing) were handling > overlapping memory areas. While there were no explicitly noticed bugs > here (yet), it is best to fix this so that the copying will always be > safe. > > Instead of making a new memmove function that

[PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-20 Thread Kees Cook
Two uses of memcpy (screen scrolling and ELF parsing) were handling overlapping memory areas. While there were no explicitly noticed bugs here (yet), it is best to fix this so that the copying will always be safe. Instead of making a new memmove function that might collide with other memmove

[PATCH 4/5] x86, boot: Make memcpy handle overlaps

2016-04-20 Thread Kees Cook
Two uses of memcpy (screen scrolling and ELF parsing) were handling overlapping memory areas. While there were no explicitly noticed bugs here (yet), it is best to fix this so that the copying will always be safe. Instead of making a new memmove function that might collide with other memmove