From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ast-bpf:relo_core 2/11] tools/lib/bpf/relo_core.c:50:6: error: no previous prototype for 'libbpf_print'
Date: Fri, 15 Oct 2021 08:08:00 +0800 [thread overview]
Message-ID: <202110150858.3GKeLSjm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git relo_core
head: f19d8aee9c6849dbfd77bc472b7b5c9bb28f329f
commit: 96649f75bfb209c3562106becb7bed3e37b05c82 [2/11] bpf: Prepare relo_core.c for kernel duty.
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 11.2.0
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=96649f75bfb209c3562106becb7bed3e37b05c82
git remote add ast-bpf https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git
git fetch --no-tags ast-bpf relo_core
git checkout 96649f75bfb209c3562106becb7bed3e37b05c82
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=m68k
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 >>):
>> tools/lib/bpf/relo_core.c:50:6: error: no previous prototype for 'libbpf_print' [-Werror=missing-prototypes]
50 | void libbpf_print(enum libbpf_print_level level,
| ^~~~~~~~~~~~
tools/lib/bpf/relo_core.c: In function 'bpf_core_apply_relo_insn':
>> tools/lib/bpf/relo_core.c:1363:1: error: the frame size of 1136 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
1363 | }
| ^
cc1: all warnings being treated as errors
vim +/libbpf_print +50 tools/lib/bpf/relo_core.c
43
44 enum libbpf_print_level {
45 LIBBPF_WARN,
46 LIBBPF_INFO,
47 LIBBPF_DEBUG,
48 };
49 __attribute__((format(printf, 2, 3)))
> 50 void libbpf_print(enum libbpf_print_level level,
51 const char *format, ...)
52 {
53 va_list args;
54
55 va_start(args, format);
56 vprintk(format, args);
57 va_end(args);
58 }
59 #define __pr(level, fmt, ...) \
60 do { \
61 libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__); \
62 } while (0)
63
---
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: 61330 bytes --]
reply other threads:[~2021-10-15 0:09 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=202110150858.3GKeLSjm-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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