public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [ast-bpf:memalloc 1/7] kernel/bpf/memalloc.c:158:10: error: call to undeclared function 'get_mem_cgroup_from_objcg'; ISO C99 and later do not support implicit function declarations
Date: Fri, 15 Jul 2022 09:55:17 +0800	[thread overview]
Message-ID: <202207150914.NwhVRROz-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git memalloc
head:   02e9f2eaae15bfdbc6ab59716ec63c471daa8822
commit: a4e9a79dc137aa2436d0217a0ac415e884cfa862 [1/7] bpf: Introduce any context BPF specific memory allocator.
config: hexagon-randconfig-r006-20220714 (https://download.01.org/0day-ci/archive/20220715/202207150914.NwhVRROz-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 2da550140aa98cf6a3e96417c87f1e89e3a26047)
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://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git/commit/?id=a4e9a79dc137aa2436d0217a0ac415e884cfa862
        git remote add ast-bpf https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git
        git fetch --no-tags ast-bpf memalloc
        git checkout a4e9a79dc137aa2436d0217a0ac415e884cfa862
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash kernel/bpf/

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

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

>> kernel/bpf/memalloc.c:158:10: error: call to undeclared function 'get_mem_cgroup_from_objcg'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                   return get_mem_cgroup_from_objcg(c->objcg);
                          ^
   kernel/bpf/memalloc.c:158:10: note: did you mean 'get_mem_cgroup_from_mm'?
   include/linux/memcontrol.h:1271:34: note: 'get_mem_cgroup_from_mm' declared here
   static inline struct mem_cgroup *get_mem_cgroup_from_mm(struct mm_struct *mm)
                                    ^
>> kernel/bpf/memalloc.c:158:10: warning: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct mem_cgroup *' [-Wint-conversion]
                   return get_mem_cgroup_from_objcg(c->objcg);
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   1 warning and 1 error generated.


vim +/get_mem_cgroup_from_objcg +158 kernel/bpf/memalloc.c

   154	
   155	static struct mem_cgroup *get_memcg(const struct bpf_mem_cache *c)
   156	{
   157		if (c->objcg)
 > 158			return get_mem_cgroup_from_objcg(c->objcg);
   159	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-15  1:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202207150914.NwhVRROz-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ast@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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