From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: kernel/bpf/trampoline.c:9:31: sparse: sparse: symbol 'bpf_extension_verifier_ops' was not declared. Should it be static?
Date: Sun, 7 Jan 2024 13:02:27 +0800 [thread overview]
Message-ID: <202401071250.XKU9ZxU4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 52b1853b080a082ec3749c3a9577f6c71b1d4a90
commit: be8704ff07d2374bcc5c675526f95e70c6459683 bpf: Introduce dynamic program extensions
date: 4 years ago
config: x86_64-randconfig-121-20240106 (https://download.01.org/0day-ci/archive/20240107/202401071250.XKU9ZxU4-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240107/202401071250.XKU9ZxU4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401071250.XKU9ZxU4-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/trampoline.c:9:31: sparse: sparse: symbol 'bpf_extension_verifier_ops' was not declared. Should it be static?
>> kernel/bpf/trampoline.c:11:27: sparse: sparse: symbol 'bpf_extension_prog_ops' was not declared. Should it be static?
kernel/bpf/trampoline.c:320:9: sparse: sparse: context imbalance in '__bpf_prog_enter' - wrong count at exit
kernel/bpf/trampoline.c: note: in included file (through include/linux/workqueue.h, include/linux/bpf.h):
include/linux/rcupdate.h:669:9: sparse: sparse: context imbalance in '__bpf_prog_exit' - unexpected unlock
vim +/bpf_extension_verifier_ops +9 kernel/bpf/trampoline.c
7
8 /* dummy _ops. The verifier will operate on target program's ops. */
> 9 const struct bpf_verifier_ops bpf_extension_verifier_ops = {
10 };
> 11 const struct bpf_prog_ops bpf_extension_prog_ops = {
12 };
13
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-07 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 5:02 kernel test robot [this message]
2024-01-09 7:03 kernel test robot
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=202401071250.XKU9ZxU4-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®