From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [perf-tools-next:tmp.perf-tools-next 14/20] util/header.c:2549:36: error: format '%d' expects argument of type 'int', but argument 4 has type 'ssize_t' {aka 'long int'}
Date: Thu, 02 Apr 2026 03:09:24 +0200 [thread overview]
Message-ID: <202604020316.eOOSUBEU-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: SeungJu Cheon <suunj1331@gmail.com>
CC: Namhyung Kim <namhyung@kernel.org>
CC: Ian Rogers <irogers@google.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
head: 98fb63998c72ab248ea1e02aa96a8e1f8e6d8a33
commit: b604ccac3472cfb0423842b0dc562304144e2d17 [14/20] perf header: Validate build_id filename length to prevent buffer overflow
:::::: branch date: 49 minutes ago
:::::: commit date: 2 hours ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260402/202604020316.eOOSUBEU-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260402/202604020316.eOOSUBEU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202604020316.eOOSUBEU-lkp@intel.com/
All errors (new ones prefixed by >>):
Makefile.config:577: No elfutils/debuginfod.h found, no debuginfo server support, please install libdebuginfod-dev/elfutils-debuginfod-client-devel or equivalent
Makefile.config:964: No libllvm 13+ found, slower source file resolution, please install llvm-devel/llvm-dev
Makefile.config:1160: Rust is not found. Test workloads with rust are disabled.
PERF_VERSION = 7.0.rc4.gb604ccac3472
In file included from util/header.c:38:
util/header.c: In function 'perf_header__read_build_ids_abi_quirk':
>> util/header.c:2549:36: error: format '%d' expects argument of type 'int', but argument 4 has type 'ssize_t' {aka 'long int'} [-Werror=format=]
2549 | pr_warning("invalid build_id filename length %d\n", len);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
util/debug.h:20:21: note: in definition of macro 'pr_fmt'
20 | #define pr_fmt(fmt) fmt
| ^~~
util/header.c:2549:25: note: in expansion of macro 'pr_warning'
2549 | pr_warning("invalid build_id filename length %d\n", len);
| ^~~~~~~~~~
util/header.c:2549:71: note: format string is defined here
2549 | pr_warning("invalid build_id filename length %d\n", len);
| ~^
| |
| int
| %ld
util/header.c: In function 'perf_header__read_build_ids':
util/header.c:2596:36: error: format '%d' expects argument of type 'int', but argument 4 has type 'ssize_t' {aka 'long int'} [-Werror=format=]
2596 | pr_warning("invalid build_id filename length %d\n", len);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
util/debug.h:20:21: note: in definition of macro 'pr_fmt'
20 | #define pr_fmt(fmt) fmt
| ^~~
util/header.c:2596:25: note: in expansion of macro 'pr_warning'
2596 | pr_warning("invalid build_id filename length %d\n", len);
| ^~~~~~~~~~
util/header.c:2596:71: note: format string is defined here
2596 | pr_warning("invalid build_id filename length %d\n", len);
| ~^
| |
| int
| %ld
cc1: all warnings being treated as errors
make[4]: *** [tools/build/Makefile.build:95: util/header.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [tools/build/Makefile.build:158: util] Error 2
make[2]: *** [Makefile.perf:797: perf-util-in.o] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile.perf:289: sub-make] Error 2
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-02 1:10 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=202604020316.eOOSUBEU-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.