From: kernel test robot <oliver.sang@intel.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
<linux-perf-users@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [tip:perf/core] [perf/core] 166f10836a: perf-sanity-tests.Object_code_reading.fail
Date: Thu, 9 Jul 2026 12:36:57 +0800 [thread overview]
Message-ID: <202607091054.7c96d6c6-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/tip/tip.git perf/core
in testcase: perf-sanity-tests
version:
with following parameters:
perf_compiler: clang
group: group-00
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 224 threads 4 sockets Intel(R) Xeon(R) Platinum 8380H CPU @ 2.90GHz (Cooper Lake) with 192G 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/202607091054.7c96d6c6-lkp@intel.com
2026-07-07 00:10:32 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 ----
...
Bytes read match those read by objdump
Reading object code for memory address: 0x7feb8f2134fa
File is: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
On file address is: 0x204fa
Objdump command is: objdump -z -d --start-address=0x204fa --stop-address=0x2057a /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
Bytes read match those read by objdump
Reading object code for memory address: 0
thread__find_map failed
---- end(-1) ----
23: Object code reading : FAILED!
=== Test Summary ===
Passed main tests : 0
Passed subtests : 0
Skipped tests : 0
Failed tests : 1
List of failed tests:
23: Object code reading
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260709/202607091054.7c96d6c6-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-09 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:36 kernel test robot [this message]
2026-07-09 9:04 ` [tip:perf/core] [perf/core] 166f10836a: perf-sanity-tests.Object_code_reading.fail Mi, Dapeng
2026-07-10 8:41 ` Oliver Sang
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=202607091054.7c96d6c6-lkp@intel.com \
--to=oliver.sang@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 \
--cc=x86@kernel.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