From: kernel test robot <yi1.lai@intel.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org, yi1.lai@intel.com
Subject: [linus:master] [perf/core] 166f10836a: perf-sanity-tests.Object_code_reading.fail
Date: Tue, 15 Sep 2026 15:45:00 +0800 [thread overview]
Message-ID: <202609151503.cb02f753-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "perf-sanity-tests.Object_code_reading.fail" on:
commit: 166f10836a653dfa280d4335603b52f685b8b1ef ("perf/core: Fix kernel register info leak via hardware skid") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linux-next/master 68142f986ff04b2b70b31db00f719bf690f64a9a]
in testcase: perf-sanity-tests
with following parameters:
perf_compiler: gcc
group: group-00
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 20 threads 1 sockets (Commet Lake) with 16G memory
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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202609151503.cb02f753-lkp@intel.com
2026-09-14 10:03:47 sudo ASAN_OPTIONS=fast_unwind_on_malloc=0 /usr/src/linux-perf-x86_64-rhel-9.4-bpf-166f10836a653dfa280d4335603b52f685b8b1ef/tools/perf/perf test 23 -v
23: Object code reading : Running (1 active)
---- start ----
...
Reading object code for memory address: 0x7f6d46bf44de File is: /usr/lib/x86_64-linux-gnu/libc.so.6
Already tested /usr/lib/x86_64-linux-gnu/libc.so.6 @ 0xff4de - skipping Reading object code for memory address: 0x7f6d46bf44de File is: /usr/lib/x86_64-linux-gnu/libc.so.6
Already tested /usr/lib/x86_64-linux-gnu/libc.so.6 @ 0xff4de - skipping Reading object code for memory address: 0 thread__find_map failed
---- end(-1) ----
23: Object code reading : FAILED!
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260915/202609151503.cb02f753-lkp@intel.com
This defect was originally reported on the perf/core branch (see https://lore.kernel.org/oe-lkp/202607091054.7c96d6c6-lkp@intel.com/). Since the culprit patch has now been merged into the mainline kernel, we have re-submitted the report to ensure proper tracking.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-15 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:45 kernel test robot [this message]
2026-09-15 9:27 ` Mi, Dapeng
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=202609151503.cb02f753-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.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®