From: kernel test robot <lkp@intel.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>
Subject: kernel/bpf/btf.c:5346:22: warning: function might be possible candidate for 'gnu_printf' format attribute
Date: Fri, 4 Jun 2021 16:22:38 +0800 [thread overview]
Message-ID: <202106041636.fjKIs9Jc-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
Hi Alan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f88cd3fb9df228e5ce4e13ec3dbad671ddb2146e
commit: 31d0bc81637d8d974a6dad9827b765b4b70c89d7 bpf: Move to generic BTF show support, apply it to seq files/strings
date: 8 months ago
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Ubuntu 6.4.0-17ubuntu1) 6.4.0 20180424
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=31d0bc81637d8d974a6dad9827b765b4b70c89d7
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 31d0bc81637d8d974a6dad9827b765b4b70c89d7
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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: In function 'btf_seq_show':
>> kernel/bpf/btf.c:5346: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:5383: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 +5346 kernel/bpf/btf.c
5342
5343 static void btf_seq_show(struct btf_show *show, const char *fmt,
5344 va_list args)
5345 {
> 5346 seq_vprintf((struct seq_file *)show->target, fmt, args);
5347 }
5348
---
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: 45431 bytes --]
next reply other threads:[~2021-06-04 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 8:22 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-13 18:27 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=202106041636.fjKIs9Jc-lkp@intel.com \
--to=lkp@intel.com \
--cc=alan.maguire@oracle.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
all inboxes | Powered by JetHome®