mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v3] x86/boot: Warn on future overlapping memcpy() use
Date: Fri, 29 Apr 2016 07:56:51 +0800	[thread overview]
Message-ID: <201604290750.0i0B1xer%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160428234636.GA32363@www.outflux.net>

[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]

Hi,

[auto build test ERROR on tip/auto-latest]
[cannot apply to tip/x86/core v4.6-rc5 next-20160428]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Kees-Cook/x86-boot-Warn-on-future-overlapping-memcpy-use/20160429-075026
config: i386-tinyconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All error/warnings (new ones prefixed by >>):

   arch/x86/boot/compressed/string.c: In function 'memmove':
>> arch/x86/boot/compressed/string.c:56:10: warning: implicit declaration of function 'memcpy' [-Wimplicit-function-declaration]
      return memcpy(dest, src, n);
             ^
>> arch/x86/boot/compressed/string.c:56:10: warning: return makes pointer from integer without a cast [-Wint-conversion]
   arch/x86/boot/compressed/string.c: At top level:
>> arch/x86/boot/compressed/string.c:65:7: error: conflicting types for 'memcpy'
    void *memcpy(void *dest, const void *src, size_t n)
          ^
   arch/x86/boot/compressed/string.c:56:10: note: previous implicit declaration of 'memcpy' was here
      return memcpy(dest, src, n);
             ^
   arch/x86/boot/compressed/string.c: In function 'memcpy':
>> arch/x86/boot/compressed/string.c:68:3: warning: implicit declaration of function 'warn' [-Wimplicit-function-declaration]
      warn("Avoiding potentially unsafe overlapping memcpy()!");
      ^

vim +/memcpy +65 arch/x86/boot/compressed/string.c

    50	void *memmove(void *dest, const void *src, size_t n)
    51	{
    52		unsigned char *d = dest;
    53		const unsigned char *s = src;
    54	
    55		if (d <= s || d - s >= n)
  > 56			return memcpy(dest, src, n);
    57	
    58		while (n-- > 0)
    59			d[n] = s[n];
    60	
    61		return dest;
    62	}
    63	
    64	/* Detect and warn about potential overlaps, but handle them with memmove. */
  > 65	void *memcpy(void *dest, const void *src, size_t n)
    66	{
    67		if (dest > src && dest - src < n) {
  > 68			warn("Avoiding potentially unsafe overlapping memcpy()!");
    69			return memmove(dest, src, n);
    70		}
    71		return __memcpy(dest, src, n);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6283 bytes --]

  parent reply	other threads:[~2016-04-28 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 23:46 Kees Cook
2016-04-28 23:49 ` Kees Cook
2016-04-28 23:56 ` kbuild test robot [this message]
2016-04-29  0:15   ` Kees Cook

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=201604290750.0i0B1xer%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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®