From: kernel test robot <lkp@intel.com>
To: Rafael David Tinoco <rafaeldtinoco@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrii Nakryiko <andrii@kernel.org>
Subject: [bpf-next:master 1/1] libbpf.c:9012:37: error: '%s' directive output may be truncated writing up to 127 bytes into a region of size between 62 and 189
Date: Wed, 15 Sep 2021 04:20:16 +0800 [thread overview]
Message-ID: <202109150409.WuS6Qtb3-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3742 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
head: 467b3225553a7945a896efabffb0b24871561ce3
commit: 467b3225553a7945a896efabffb0b24871561ce3 [1/1] libbpf: Introduce legacy kprobe events support
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=467b3225553a7945a896efabffb0b24871561ce3
git remote add bpf-next https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
git fetch --no-tags bpf-next master
git checkout 467b3225553a7945a896efabffb0b24871561ce3
# 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 errors (new ones prefixed by >>):
libbpf.c: In function 'poke_kprobe_events':
>> libbpf.c:9012:37: error: '%s' directive output may be truncated writing up to 127 bytes into a region of size between 62 and 189 [-Werror=format-truncation=]
9012 | snprintf(cmd, sizeof(cmd), "%c:%s %s",
| ^~
libbpf.c:9012:3: note: 'snprintf' output between 4 and 258 bytes into a destination of size 192
9012 | snprintf(cmd, sizeof(cmd), "%c:%s %s",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9013 | retprobe ? 'r' : 'p',
| ~~~~~~~~~~~~~~~~~~~~~
9014 | probename,
| ~~~~~~~~~~
9015 | offset ? probefunc : name);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[5]: *** [tools/build/Makefile.build:96: tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o] Error 1
make[4]: *** [Makefile:161: tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2
make[3]: *** [Makefile:45: tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2
make[2]: *** [Makefile:72: bpf/resolve_btfids] Error 2
make[1]: *** [Makefile:1374: tools/bpf/resolve_btfids] Error 2
make[1]: Target 'modules_prepare' not remade because of errors.
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'modules_prepare' not remade because of errors.
--
libbpf.c: In function 'poke_kprobe_events':
>> libbpf.c:9012:37: error: '%s' directive output may be truncated writing up to 127 bytes into a region of size between 62 and 189 [-Werror=format-truncation=]
9012 | snprintf(cmd, sizeof(cmd), "%c:%s %s",
| ^~
libbpf.c:9012:3: note: 'snprintf' output between 4 and 258 bytes into a destination of size 192
9012 | snprintf(cmd, sizeof(cmd), "%c:%s %s",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9013 | retprobe ? 'r' : 'p',
| ~~~~~~~~~~~~~~~~~~~~~
9014 | probename,
| ~~~~~~~~~~
9015 | offset ? probefunc : name);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[5]: *** [tools/build/Makefile.build:96: tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o] Error 1
make[4]: *** [Makefile:161: tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2
make[3]: *** [Makefile:45: tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2
make[2]: *** [Makefile:72: bpf/resolve_btfids] Error 2
make[1]: *** [Makefile:1374: tools/bpf/resolve_btfids] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
---
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: 42013 bytes --]
reply other threads:[~2021-09-14 20:21 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=202109150409.WuS6Qtb3-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafaeldtinoco@gmail.com \
/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®