From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC bpf 2/2] btf: adapt relo_core for kernel compilation
Date: Thu, 09 Sep 2021 23:38:21 +0800 [thread overview]
Message-ID: <202109092331.7bPqKfAl-lkp@intel.com> (raw)
In-Reply-To: <20210909133153.48994-3-mcroce@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]
Hi Matteo,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on bpf/master]
url: https://github.com/0day-ci/linux/commits/Matteo-Croce/bpf-kernel-CO-RE-relocation/20210909-213900
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
config: sh-allmodconfig (attached as .config)
compiler: sh4-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://github.com/0day-ci/linux/commit/c195b385facdf03a4ce9fc7a00d370b1753de6b6
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Matteo-Croce/bpf-kernel-CO-RE-relocation/20210909-213900
git checkout c195b385facdf03a4ce9fc7a00d370b1753de6b6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/bpf/relo_core.c:168:1: warning: no previous prototype for 'skip_mods_and_typedefs' [-Wmissing-prototypes]
168 | skip_mods_and_typedefs(const struct btf *btf, __u32 id, __u32 *res_id)
| ^~~~~~~~~~~~~~~~~~~~~~
kernel/bpf/relo_core.c: In function 'bpf_core_apply_relo_insn':
>> kernel/bpf/relo_core.c:1457:1: warning: the frame size of 2188 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1457 | }
| ^
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_PDC
Depends on SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && HAS_DMA
Selected by
- SND_ATMEL_SOC_SSC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC
- SND_ATMEL_SOC_SSC_PDC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && ATMEL_SSC
vim +/skip_mods_and_typedefs +168 kernel/bpf/relo_core.c
166
167 const struct btf_type *
> 168 skip_mods_and_typedefs(const struct btf *btf, __u32 id, __u32 *res_id)
169 {
170 const struct btf_type *t = btf__type_by_id(btf, id);
171
172 if (res_id)
173 *res_id = id;
174
175 while (btf_type_is_modifier(t) || btf_type_is_typedef(t)) {
176 if (res_id)
177 *res_id = t->type;
178 t = btf__type_by_id(btf, t->type);
179 }
180
181 return t;
182 }
183
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 55129 bytes --]
next prev parent reply other threads:[~2021-09-09 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 13:31 [RFC bpf 0/2] bpf: kernel CO-RE relocation Matteo Croce
2021-09-09 13:31 ` [RFC bpf 1/2] btf: copy relo_core from tools to kernel Matteo Croce
2021-09-09 13:31 ` [RFC bpf 2/2] btf: adapt relo_core for kernel compilation Matteo Croce
2021-09-09 15:38 ` kernel test robot [this message]
2021-09-09 18:23 ` Alexei Starovoitov
2021-09-17 1:21 ` Matteo Croce
2021-09-17 4:12 ` Alexei Starovoitov
2021-09-17 17:45 ` Andrii Nakryiko
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=202109092331.7bPqKfAl-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.