linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org, dvyukov@google.com,
	aryabinin@virtuozzo.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/stackdepot.c: use a non-instrumented version of memcpy()
Date: Fri, 18 May 2018 09:04:32 +0800	[thread overview]
Message-ID: <201805180757.Els81pW3%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180516153434.24479-1-glider@google.com>

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

Hi Alexander,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Alexander-Potapenko/lib-stackdepot-c-use-a-non-instrumented-version-of-memcpy/20180518-015328
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=sh 

All errors (new ones prefixed by >>):

   lib/stackdepot.c: In function 'depot_alloc_stack':
>> lib/stackdepot.c:143:2: error: implicit declaration of function '__memcpy'; did you mean 'memcpy'? [-Werror=implicit-function-declaration]
     __memcpy(stack->entries, entries, size * sizeof(unsigned long));
     ^~~~~~~~
     memcpy
   cc1: some warnings being treated as errors

vim +143 lib/stackdepot.c

   106	
   107	/* Allocation of a new stack in raw storage */
   108	static struct stack_record *depot_alloc_stack(unsigned long *entries, int size,
   109			u32 hash, void **prealloc, gfp_t alloc_flags)
   110	{
   111		int required_size = offsetof(struct stack_record, entries) +
   112			sizeof(unsigned long) * size;
   113		struct stack_record *stack;
   114	
   115		required_size = ALIGN(required_size, 1 << STACK_ALLOC_ALIGN);
   116	
   117		if (unlikely(depot_offset + required_size > STACK_ALLOC_SIZE)) {
   118			if (unlikely(depot_index + 1 >= STACK_ALLOC_MAX_SLABS)) {
   119				WARN_ONCE(1, "Stack depot reached limit capacity");
   120				return NULL;
   121			}
   122			depot_index++;
   123			depot_offset = 0;
   124			/*
   125			 * smp_store_release() here pairs with smp_load_acquire() from
   126			 * |next_slab_inited| in depot_save_stack() and
   127			 * init_stack_slab().
   128			 */
   129			if (depot_index + 1 < STACK_ALLOC_MAX_SLABS)
   130				smp_store_release(&next_slab_inited, 0);
   131		}
   132		init_stack_slab(prealloc);
   133		if (stack_slabs[depot_index] == NULL)
   134			return NULL;
   135	
   136		stack = stack_slabs[depot_index] + depot_offset;
   137	
   138		stack->hash = hash;
   139		stack->size = size;
   140		stack->handle.slabindex = depot_index;
   141		stack->handle.offset = depot_offset >> STACK_ALLOC_ALIGN;
   142		stack->handle.valid = 1;
 > 143		__memcpy(stack->entries, entries, size * sizeof(unsigned long));
   144		depot_offset += required_size;
   145	
   146		return stack;
   147	}
   148	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47759 bytes --]

      parent reply	other threads:[~2018-05-18  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 15:34 Alexander Potapenko
2018-05-16 16:47 ` Andrey Ryabinin
2018-05-17  8:53   ` Alexander Potapenko
2018-05-18  1:04 ` kbuild test robot [this message]

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=201805180757.Els81pW3%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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