From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 bpf-next 2/8] bpf: move to generic BTF show support, apply it to seq files/strings
Date: Fri, 26 Jun 2020 16:13:58 +0800 [thread overview]
Message-ID: <202006261644.nYGRaM5n%lkp@intel.com> (raw)
In-Reply-To: <1592914031-31049-3-git-send-email-alan.maguire@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hi Alan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Alan-Maguire/bpf-printk-add-BTF-based-type-printing/20200623-201410
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: i386-randconfig-a013-20200624 (attached as .config)
compiler: gcc-6 (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
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/btf.c:4192:2: warning: initialized field overwritten [-Woverride-init]
0, /* avoid empty array */
^
kernel/bpf/btf.c:4192:2: note: (near initialization for 'bpf_ctx_convert_map[22]')
kernel/bpf/btf.c:5269:6: warning: no previous prototype for 'btf_type_show' [-Wmissing-prototypes]
void btf_type_show(const struct btf *btf, u32 type_id, void *obj,
^~~~~~~~~~~~~
kernel/bpf/btf.c: In function 'btf_seq_show':
>> kernel/bpf/btf.c:5286:22: warning: function might be possible candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
seq_vprintf((struct seq_file *)show->target, fmt, args);
^~~~~~~~
kernel/bpf/btf.c: In function 'btf_snprintf_show':
kernel/bpf/btf.c:5316:2: warning: function might be possible candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
len = vsnprintf(show->target, ssnprintf->len_left, fmt, args);
^~~
vim +/gnu_printf +5286 kernel/bpf/btf.c
5280
5281 static void btf_seq_show(struct btf_show *show, const char *fmt, ...)
5282 {
5283 va_list args;
5284
5285 va_start(args, fmt);
> 5286 seq_vprintf((struct seq_file *)show->target, fmt, args);
5287 va_end(args);
5288 }
5289
---
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: 31592 bytes --]
next prev parent reply other threads:[~2020-06-26 8:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 12:07 [PATCH v3 bpf-next 0/8] bpf, printk: add BTF-based type printing Alan Maguire
2020-06-23 12:07 ` [PATCH v3 bpf-next 1/8] bpf: provide function to get vmlinux BTF information Alan Maguire
2020-06-23 12:07 ` [PATCH v3 bpf-next 2/8] bpf: move to generic BTF show support, apply it to seq files/strings Alan Maguire
2020-06-23 18:14 ` kernel test robot
2020-06-26 8:13 ` kernel test robot [this message]
2020-06-23 12:07 ` [PATCH v3 bpf-next 3/8] checkpatch: add new BTF pointer format specifier Alan Maguire
2020-06-23 12:07 ` [PATCH v3 bpf-next 4/8] printk: add type-printing %pT format specifier which uses BTF Alan Maguire
2020-06-23 12:40 ` Andy Shevchenko
2020-06-23 13:11 ` Rasmus Villemoes
2020-06-26 10:15 ` Petr Mladek
2020-06-26 11:37 ` Alan Maguire
2020-06-29 9:43 ` Petr Mladek
2020-06-23 12:07 ` [PATCH v3 bpf-next 5/8] printk: initialize vmlinux BTF outside of printk in late_initcall() Alan Maguire
2020-06-23 12:07 ` [PATCH v3 bpf-next 6/8] printk: extend test_printf to test %pT BTF-based format specifier Alan Maguire
2020-06-23 13:02 ` Andy Shevchenko
2020-06-23 12:07 ` [PATCH v3 bpf-next 7/8] bpf: add support for %pT format specifier for bpf_trace_printk() helper Alan Maguire
2020-06-23 13:04 ` Andy Shevchenko
2020-06-23 12:07 ` [PATCH v3 bpf-next 8/8] bpf/selftests: add tests for %pT format specifier Alan Maguire
2020-06-23 18:16 ` Andrii Nakryiko
2020-06-30 11:31 ` [PATCH v3 bpf-next 0/8] bpf, printk: add BTF-based type printing Sergey Senozhatsky
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=202006261644.nYGRaM5n%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.