public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] mm, slob: Rewrite SLOB using segregated free list
Date: Thu, 21 Oct 2021 04:22:27 +0800	[thread overview]
Message-ID: <202110210402.brCmSha5-lkp@intel.com> (raw)
In-Reply-To: <20211020135535.517236-1-42.hyeyoo@gmail.com>

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

Hi Hyeonggon,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linux/master]
[also build test ERROR on linus/master v5.15-rc6 next-20211020]
[cannot apply to hnaz-mm/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Hyeonggon-Yoo/mm-slob-Rewrite-SLOB-using-segregated-free-list/20211020-215705
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ec681c53f8d2d0ee362ff67f5b98dd8263c15002
config: i386-randconfig-r003-20211019 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9660563950aaed54020bfdf0be07e7096a9553e4)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/e2ba7ee42ed802d48dd0ea4ff0fe07096d115c11
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Hyeonggon-Yoo/mm-slob-Rewrite-SLOB-using-segregated-free-list/20211020-215705
        git checkout e2ba7ee42ed802d48dd0ea4ff0fe07096d115c11
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> mm/slob.c:603:16: error: use of undeclared identifier '_RET_IP'; did you mean 'NET_IPX'?
           trace_kmalloc(_RET_IP, ret, size, s->size, gfp);
                         ^~~~~~~
                         NET_IPX
   include/uapi/linux/sysctl.h:210:2: note: 'NET_IPX' declared here
           NET_IPX=6,
           ^
>> mm/slob.c:604:12: error: expected ';' after return statement
           return ret
                     ^
                     ;
   2 errors generated.


vim +603 mm/slob.c

   597	
   598	#ifdef CONFIG_TRACING
   599	void *kmem_cache_alloc_trace(struct kmem_cache *s, gfp_t gfp, size_t size)
   600	{
   601		void *ret = slob_alloc_node(s, gfp, NUMA_NO_NODE);
   602	
 > 603		trace_kmalloc(_RET_IP, ret, size, s->size, gfp);
 > 604		return ret
   605	}
   606	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

           reply	other threads:[~2021-10-20 20:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20211020135535.517236-1-42.hyeyoo@gmail.com>]

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=202110210402.brCmSha5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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