From: kernel test robot <lkp@intel.com>
To: Stanislav Fomichev <sdf@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>
Subject: [linux-next:master 5835/8914] kernel/bpf/bpf_lsm.c:51:26: warning: variable 'args' set but not used
Date: Sun, 10 Jul 2022 23:26:58 +0800 [thread overview]
Message-ID: <202207102321.jwphabAL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f2528c29385819a84480cacef4886b049761e2c5
commit: 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e [5835/8914] bpf: per-cgroup lsm flavor
config: arm-buildonly-randconfig-r003-20220710 (https://download.01.org/0day-ci/archive/20220710/202207102321.jwphabAL-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 6ce63e267aab79ca87bf63453d34dd3909ab978d)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e
# 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=arm 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 warnings (new ones prefixed by >>):
>> kernel/bpf/bpf_lsm.c:51:26: warning: variable 'args' set but not used [-Wunused-but-set-variable]
const struct btf_param *args;
^
1 warning generated.
vim +/args +51 kernel/bpf/bpf_lsm.c
47
48 void bpf_lsm_find_cgroup_shim(const struct bpf_prog *prog,
49 bpf_func_t *bpf_func)
50 {
> 51 const struct btf_param *args;
52
53 if (btf_type_vlen(prog->aux->attach_func_proto) < 1 ||
54 btf_id_set_contains(&bpf_lsm_current_hooks,
55 prog->aux->attach_btf_id)) {
56 *bpf_func = __cgroup_bpf_run_lsm_current;
57 return;
58 }
59
60 args = btf_params(prog->aux->attach_func_proto);
61
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-10 15:27 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=202207102321.jwphabAL-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=kafai@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=sdf@google.com \
/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