All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC bpf-next 1/2] bpf: add a kallsyms BPF iterator
Date: Sat, 25 Jun 2022 12:33:19 +0800	[thread overview]
Message-ID: <202206251225.nDavCyPn-lkp@intel.com> (raw)
In-Reply-To: <1656089118-577-2-git-send-email-alan.maguire@oracle.com>

Hi Alan,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on bpf-next/master]

url:    https://github.com/intel-lab-lkp/linux/commits/Alan-Maguire/bpf-add-a-kallsyms-BPF-iterator/20220625-004938
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: mips-randconfig-r031-20220624
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 42a7ddb428c999229491b0effbb1a4059149fba8)
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
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/intel-lab-lkp/linux/commit/bee65a1c850426a5b6f798753bb50c74a6dca06b
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Alan-Maguire/bpf-add-a-kallsyms-BPF-iterator/20220625-004938
        git checkout bee65a1c850426a5b6f798753bb50c74a6dca06b
        # 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=mips SHELL=/bin/bash

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

All warnings (new ones prefixed by >>):

   kernel/kallsyms.c:591:12: warning: no previous prototype for function 'arch_get_kallsym' [-Wmissing-prototypes]
   int __weak arch_get_kallsym(unsigned int symnum, unsigned long *value,
              ^
   kernel/kallsyms.c:591:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   int __weak arch_get_kallsym(unsigned int symnum, unsigned long *value,
   ^
   static 
>> kernel/kallsyms.c:839:36: warning: unused variable 'bpf_iter_kallsyms_ops' [-Wunused-const-variable]
   static const struct seq_operations bpf_iter_kallsyms_ops = {
                                      ^
   2 warnings generated.


vim +/bpf_iter_kallsyms_ops +839 kernel/kallsyms.c

   838	
 > 839	static const struct seq_operations bpf_iter_kallsyms_ops = {
   840		.start = s_start,
   841		.next = s_next,
   842		.stop = bpf_iter_s_seq_stop,
   843		.show = bpf_iter_s_seq_show,
   844	};
   845	

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

  parent reply	other threads:[~2022-06-25  4:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:45 [RFC bpf-next 0/2] bpf: add a kallsyms BPF iterator Alan Maguire
2022-06-24 16:45 ` [RFC bpf-next 1/2] " Alan Maguire
2022-06-24 22:18   ` Andrii Nakryiko
2022-06-25  4:33   ` kernel test robot [this message]
2022-06-24 16:45 ` [RFC bpf-next 2/2] selftests/bpf: add a kallsyms iter subtest Alan Maguire

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=202206251225.nDavCyPn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alan.maguire@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.