mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, Andy Lutomirski <luto@amacapital.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, kasan: Fix build failure on KASAN=y && KMEMCHECK=y kernels
Date: Mon, 19 Oct 2015 18:53:06 +0200	[thread overview]
Message-ID: <20151019165306.GB19953@pd.tnic> (raw)
In-Reply-To: <1444994933-28328-1-git-send-email-aryabinin@virtuozzo.com>

On Fri, Oct 16, 2015 at 02:28:53PM +0300, Andrey Ryabinin wrote:
> Declaration of memcpy is hidden under #ifndef CONFIG_KMEMCHECK.
> In asm/efi.h we under #ifdef CONFIG_KASAN we #undef memcpy
> thus following happens:
> 
> In file included from arch/x86/kernel/setup.c:96:0:
> ./arch/x86/include/asm/desc.h: In function ‘native_write_idt_entry’:
> ./arch/x86/include/asm/desc.h:122:2: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]
>   memcpy(&idt[entry], gate, sizeof(*gate));
>   ^
>   cc1: some warnings being treated as errors
>   make[2]: *** [arch/x86/kernel/setup.o] Error 1
> 
> We will get rid of that #undef in asm/efi.h eventually.
> But in the meanwhile move memcpy() declaration out ifdefs
> to fix build.
> 

Looks ok to me. I guess this should go together with the efi.h fix.

> Reported-by: Borislav Petkov <bp@alien8.de>

	...-and-tested-by: me

> Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> ---
>  arch/x86/include/asm/string_64.h | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/include/asm/string_64.h b/arch/x86/include/asm/string_64.h
> index e466119..ff8b9a1 100644
> --- a/arch/x86/include/asm/string_64.h
> +++ b/arch/x86/include/asm/string_64.h
> @@ -27,12 +27,11 @@ static __always_inline void *__inline_memcpy(void *to, const void *from, size_t
>     function. */
>  
>  #define __HAVE_ARCH_MEMCPY 1
> +extern void *memcpy(void *to, const void *from, size_t len);
>  extern void *__memcpy(void *to, const void *from, size_t len);
>  
>  #ifndef CONFIG_KMEMCHECK
> -#if (__GNUC__ == 4 && __GNUC_MINOR__ >= 3) || __GNUC__ > 4
> -extern void *memcpy(void *to, const void *from, size_t len);
> -#else
> +#if (__GNUC__ == 4 && __GNUC_MINOR__ < 3) || __GNUC__ < 4
>  #define memcpy(dst, src, len)					\
>  ({								\
>  	size_t __len = (len);					\
> -- 
> 2.4.9

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2015-10-19 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 21:47 ./arch/x86/include/asm/desc.h:122:2: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration] Borislav Petkov
2015-10-15  7:31 ` Andrey Ryabinin
2015-10-16 11:28 ` [PATCH] x86, kasan: Fix build failure on KASAN=y && KMEMCHECK=y kernels Andrey Ryabinin
2015-10-19 16:53   ` Borislav Petkov [this message]
2015-10-19 17:48   ` [tip:x86/urgent] x86, kasan: Fix build failure on KASAN= y " tip-bot for Andrey Ryabinin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151019165306.GB19953@pd.tnic \
    --to=bp@alien8.de \
    --cc=aryabinin@virtuozzo.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®