Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1385718

Re: [PATCH] x86/boot: Rename overlapping memcpy() to memmove()

Show all headers | View raw

On Sat, Apr 23, 2016 at 4:08 AM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * Kees Cook <keescook@chromium.org> wrote:
>
>> --- a/arch/x86/boot/compressed/string.c
>> +++ b/arch/x86/boot/compressed/string.c
>> @@ -1,7 +1,13 @@
>> +/*
>> + * This provides an optimized implementation of memcpy, and a simplified
>> + * implementation of memset and memmove, to avoid problems with the
>> + * built-in implementations when running in the restricted decompression
>> + * stub environment.
>> + */
>
> Does 'built in' here mean the compiler's implementation?
>
> We cannot call kernel built-in functions yet, so we have to duplicate everything
> we might need, right?

Right, I actually mean both: we can use neither gcc nor kernel
built-ins. (I am fuzzy on why the gcc built-ins aren't available -- I
think because they're not available for standalone builds.)

-Kees

>
> Thanks,
>
>         Ingo



-- 
Kees Cook
Chrome OS & Brillo Security

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH] x86/boot: Rename overlapping memcpy() to memmove() Kees Cook <keescook@chromium.org> - 2016-04-23 00:30 +0200
  Re: [PATCH] x86/boot: Rename overlapping memcpy() to memmove() Ingo Molnar <mingo@kernel.org> - 2016-04-23 13:10 +0200
    Re: [PATCH] x86/boot: Rename overlapping memcpy() to memmove() Kees Cook <keescook@chromium.org> - 2016-04-23 21:50 +0200
      Re: [PATCH] x86/boot: Rename overlapping memcpy() to memmove() Ingo Molnar <mingo@kernel.org> - 2016-04-25 09:40 +0200

csiph-web