Re: [PATCH v1] perf inject: Factor build ID inject out into a separate tool

[kernel test robot <lkp@intel.com>]

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "likely FALSE maybe-used-uninitialized warning on old compiler"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260320223520.520454-1-irogers@google.com>
References: <20260320223520.520454-1-irogers@google.com>
TO: Ian Rogers <irogers@google.com>
TO: Peter Zijlstra <peterz@infradead.org>
TO: Ingo Molnar <mingo@redhat.com>
TO: Arnaldo Carvalho de Melo <acme@kernel.org>
TO: Namhyung Kim <namhyung@kernel.org>
TO: Alexander Shishkin <alexander.shishkin@linux.intel.com>
TO: Jiri Olsa <jolsa@kernel.org>
TO: Ian Rogers <irogers@google.com>
TO: Adrian Hunter <adrian.hunter@intel.com>
TO: James Clark <james.clark@linaro.org>
TO: linux-kernel@vger.kernel.org
TO: linux-perf-users@vger.kernel.org

Hi Ian,

kernel test robot noticed the following build errors:

[auto build test ERROR on perf-tools-next/perf-tools-next]
[also build test ERROR on tip/perf/core perf-tools/perf-tools linus/master v7.0-rc4 next-20260320]
[cannot apply to acme/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Ian-Rogers/perf-inject-Factor-build-ID-inject-out-into-a-separate-tool/20260321-191906
base:   https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link:    https://lore.kernel.org/r/20260320223520.520454-1-irogers%40google.com
patch subject: [PATCH v1] perf inject: Factor build ID inject out into a separate tool
:::::: branch date: 81 minutes ago
:::::: commit date: 81 minutes ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260321/202603211341.4yqxPbic-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/20260321/202603211341.4yqxPbic-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/202603211341.4yqxPbic-lkp@intel.com/

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All errors (new ones prefixed by >>):

   Makefile.config:576: No elfutils/debuginfod.h found, no debuginfo server support, please install libdebuginfod-dev/elfutils-debuginfod-client-devel or equivalent
   Makefile.config:963: No libllvm 13+ found, slower source file resolution, please install llvm-devel/llvm-dev
   Makefile.config:1159: Rust is not found. Test workloads with rust are disabled.
     PERF_VERSION = 7.0.rc1.g492296b4d64a
   builtin-inject.c: In function 'cmd_inject':
>> builtin-inject.c:2324:16: error: 'ret' may be used uninitialized [-Werror=maybe-uninitialized]
    2324 |         return ret;
         |                ^~~
   builtin-inject.c:2044:13: note: 'ret' was declared here
    2044 |         int ret;
         |             ^~~
   cc1: all warnings being treated as errors
   make[3]: *** [tools/build/Makefile.build:93: builtin-inject.o] Error 1
   make[3]: *** Waiting for unfinished jobs....
   make[2]: *** [Makefile.perf:770: perf-in.o] Error 2
   make[1]: *** [Makefile.perf:289: sub-make] Error 2

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki