From: kernel test robot <oliver.sang@intel.com>
To: Ian Rogers <irogers@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Namhyung Kim <namhyung@kernel.org>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <irogers@google.com>,
<acme@kernel.org>, <adrian.hunter@intel.com>,
<ajones@ventanamicro.com>, <ak@linux.intel.com>, <alex@ghiti.fr>,
<alexander.shishkin@linux.intel.com>, <anup@brainfault.org>,
<aou@eecs.berkeley.edu>, <atrajeev@linux.ibm.com>,
<blakejones@google.com>, <ctshao@google.com>,
<dapeng1.mi@linux.intel.com>, <derek.foreman@collabora.com>,
<dvyukov@google.com>, <howardchu95@gmail.com>,
<hrishikesh123s@gmail.com>, <james.clark@linaro.org>,
<jolsa@kernel.org>, <krzysztof.m.lopatowski@gmail.com>,
<leo.yan@arm.com>, <linux@treblig.org>, <mingo@redhat.com>,
<nichen@iscas.ac.cn>, <palmer@dabbelt.com>,
<peterz@infradead.org>, <pjw@kernel.org>, <ravi.bangoria@amd.com>,
<swapnil.sapkal@amd.com>, <tanze@kylinos.cn>,
<thomas.falcon@intel.com>, <tianyou.li@intel.com>,
<yujie.liu@intel.com>, <zhouquan@iscas.ac.cn>,
<oliver.sang@intel.com>
Subject: Re: [PATCH v14 32/32] perf kwork: Fix memory management of kwork_work
Date: Mon, 25 May 2026 21:51:15 +0800 [thread overview]
Message-ID: <202605251514.4b99efea-lkp@intel.com> (raw)
In-Reply-To: <20260520190538.142018-33-irogers@google.com>
Hello,
kernel test robot noticed "perf-stat-tests.perf.make.fail" on:
commit: 7f9aae3554b369864c01505b2ec02ddf6f6e12f3 ("[PATCH v14 32/32] perf kwork: Fix memory management of kwork_work")
url: https://github.com/intel-lab-lkp/linux/commits/Ian-Rogers/perf-tool-Remove-evsel-from-tool-APIs-that-pass-the-sample/20260521-061855
patch link: https://lore.kernel.org/all/20260520190538.142018-33-irogers@google.com/
patch subject: [PATCH v14 32/32] perf kwork: Fix memory management of kwork_work
in testcase: perf-stat-tests
version:
with following parameters:
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202605251514.4b99efea-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260525/202605251514.4b99efea-lkp@intel.com
==> /tmp/stderr <==
Makefile.config:661: Warning: Disabled BPF skeletons as clang (clang) is missing
Makefile.config:1134: Rust is not found. Test workloads with rust are disabled.
PERF_VERSION = 7.1.0-rc2
/usr/bin/ld: perf-in.o: in function `work_delete':
/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-7f9aae3554b369864c01505b2ec02ddf6f6e12f3/tools/perf/builtin-kwork.c:383:(.text+0x1b569b): undefined reference to `work_exit'
/usr/bin/ld: perf-in.o: in function `work_push_atom':
/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-7f9aae3554b369864c01505b2ec02ddf6f6e12f3/tools/perf/builtin-kwork.c:549:(.text+0x1b77d3): undefined reference to `work_exit'
/usr/bin/ld: perf-in.o: in function `work_pop_atom':
/usr/src/perf_selftests-x86_64-rhel-9.4-bpf-7f9aae3554b369864c01505b2ec02ddf6f6e12f3/tools/perf/builtin-kwork.c:590:(.text+0x1b7fc6): undefined reference to `work_exit'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile.perf:803: perf] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile.perf:289: sub-make] Error 2
make: *** [Makefile:76: all] Error 2
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-05-25 13:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260520190538.142018-33-irogers@google.com>]
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=202605251514.4b99efea-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ajones@ventanamicro.com \
--cc=ak@linux.intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atrajeev@linux.ibm.com \
--cc=blakejones@google.com \
--cc=ctshao@google.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=derek.foreman@collabora.com \
--cc=dvyukov@google.com \
--cc=howardchu95@gmail.com \
--cc=hrishikesh123s@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=krzysztof.m.lopatowski@gmail.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nichen@iscas.ac.cn \
--cc=oe-lkp@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=swapnil.sapkal@amd.com \
--cc=tanze@kylinos.cn \
--cc=thomas.falcon@intel.com \
--cc=tianyou.li@intel.com \
--cc=yujie.liu@intel.com \
--cc=zhouquan@iscas.ac.cn \
/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