From: kernel test robot <oliver.sang@intel.com>
To: Eugene Syromiatnikov <esyr@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-sound@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jaroslav Kysela <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.com>,
Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v2] selftests: fix relative rpath usage
Date: Sun, 25 Aug 2024 17:40:11 +0800 [thread overview]
Message-ID: <202408251749.7e390194-oliver.sang@intel.com> (raw)
In-Reply-To: <20240812165650.GA5102@asgard.redhat.com>
Hello,
kernel test robot noticed "segfault_at_ip_sp_error" on:
commit: 782e28421b3410522d5b50feb30e8fa10da44492 ("[PATCH v2] selftests: fix relative rpath usage")
url: https://github.com/intel-lab-lkp/linux/commits/Eugene-Syromiatnikov/selftests-fix-relative-rpath-usage/20240814-091042
base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git next
patch link: https://lore.kernel.org/all/20240812165650.GA5102@asgard.redhat.com/
patch subject: [PATCH v2] selftests: fix relative rpath usage
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: group-01
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
besides, we also noticed some tests failed on this change:
8afc0816f5f6213c 782e28421b3410522d5b50feb30
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:4 100% 4:4 dmesg.segfault_at_ip_sp_error
:4 100% 4:4 kernel-selftests.exec.load_address.static.0x1000.fail
:4 100% 4:4 kernel-selftests.exec.load_address.static.0x1000000.fail
:4 100% 4:4 kernel-selftests.exec.load_address.static.0x200000.fail
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/202408251749.7e390194-oliver.sang@intel.com
user :notice: [ 458.511077] 2024-08-23 12:25:42 make -j36 -C dt
user :notice: [ 458.527252] make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-782e28421b3410522d5b50feb30e8fa10da44492/tools/testing/selftests/dt'
kern :info : [ 460.458153] load_address.st[7491]: segfault at 28 ip 00007f1137a2b5e6 sp 00007ffddc0fd6d0 error 4 in load_address.static.0x1000[d5e6,7f1137a27000+7a000] likely on CPU 2 (core 2, socket 0)
kern :info : [ 460.459808] Code: 53 48 81 ec d8 00 00 00 48 89 b5 68 ff ff ff 48 89 95 38 ff ff ff 89 8d 54 ff ff ff 4c 89 85 48 ff ff ff 44 89 8d 50 ff ff ff <64> 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 48 c7 85 70 ff ff ff
All code
========
0: 53 push %rbx
1: 48 81 ec d8 00 00 00 sub $0xd8,%rsp
8: 48 89 b5 68 ff ff ff mov %rsi,-0x98(%rbp)
f: 48 89 95 38 ff ff ff mov %rdx,-0xc8(%rbp)
16: 89 8d 54 ff ff ff mov %ecx,-0xac(%rbp)
1c: 4c 89 85 48 ff ff ff mov %r8,-0xb8(%rbp)
23: 44 89 8d 50 ff ff ff mov %r9d,-0xb0(%rbp)
2a:* 64 48 8b 04 25 28 00 mov %fs:0x28,%rax <-- trapping instruction
31: 00 00
33: 48 89 45 c8 mov %rax,-0x38(%rbp)
37: 31 c0 xor %eax,%eax
39: 48 rex.W
3a: c7 .byte 0xc7
3b: 85 70 ff test %esi,-0x1(%rax)
3e: ff (bad)
3f: ff .byte 0xff
Code starting with the faulting instruction
===========================================
0: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax
7: 00 00
9: 48 89 45 c8 mov %rax,-0x38(%rbp)
d: 31 c0 xor %eax,%eax
f: 48 rex.W
10: c7 .byte 0xc7
11: 85 70 ff test %esi,-0x1(%rax)
14: ff (bad)
15: ff .byte 0xff
kern :info : [ 460.571500] load_address.st[7510]: segfault at 28 ip 00007fa9ec0045e6 sp 00007ffd3ba861b0 error 4 in load_address.static.0x200000[2045e6,7fa9ec000000+7a000] likely on CPU 2 (core 2, socket 0)
kern :info : [ 460.573155] Code: 53 48 81 ec d8 00 00 00 48 89 b5 68 ff ff ff 48 89 95 38 ff ff ff 89 8d 54 ff ff ff 4c 89 85 48 ff ff ff 44 89 8d 50 ff ff ff <64> 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 48 c7 85 70 ff ff ff
All code
========
0: 53 push %rbx
1: 48 81 ec d8 00 00 00 sub $0xd8,%rsp
8: 48 89 b5 68 ff ff ff mov %rsi,-0x98(%rbp)
f: 48 89 95 38 ff ff ff mov %rdx,-0xc8(%rbp)
16: 89 8d 54 ff ff ff mov %ecx,-0xac(%rbp)
1c: 4c 89 85 48 ff ff ff mov %r8,-0xb8(%rbp)
23: 44 89 8d 50 ff ff ff mov %r9d,-0xb0(%rbp)
2a:* 64 48 8b 04 25 28 00 mov %fs:0x28,%rax <-- trapping instruction
31: 00 00
33: 48 89 45 c8 mov %rax,-0x38(%rbp)
37: 31 c0 xor %eax,%eax
39: 48 rex.W
3a: c7 .byte 0xc7
3b: 85 70 ff test %esi,-0x1(%rax)
3e: ff (bad)
3f: ff .byte 0xff
Code starting with the faulting instruction
===========================================
0: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax
7: 00 00
9: 48 89 45 c8 mov %rax,-0x38(%rbp)
d: 31 c0 xor %eax,%eax
f: 48 rex.W
10: c7 .byte 0xc7
11: 85 70 ff test %esi,-0x1(%rax)
14: ff (bad)
15: ff .byte 0xff
kern :info : [ 460.677410] load_address.st[7529]: segfault at 28 ip 00007f9a020045e6 sp 00007ffe4bb51e10 error 4 in load_address.static.0x1000000[10045e6,7f9a02000000+7a000] likely on CPU 2 (core 2, socket 0)
kern :info : [ 460.679071] Code: 53 48 81 ec d8 00 00 00 48 89 b5 68 ff ff ff 48 89 95 38 ff ff ff 89 8d 54 ff ff ff 4c 89 85 48 ff ff ff 44 89 8d 50 ff ff ff <64> 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 48 c7 85 70 ff ff ff
All code
========
0: 53 push %rbx
1: 48 81 ec d8 00 00 00 sub $0xd8,%rsp
8: 48 89 b5 68 ff ff ff mov %rsi,-0x98(%rbp)
f: 48 89 95 38 ff ff ff mov %rdx,-0xc8(%rbp)
16: 89 8d 54 ff ff ff mov %ecx,-0xac(%rbp)
1c: 4c 89 85 48 ff ff ff mov %r8,-0xb8(%rbp)
23: 44 89 8d 50 ff ff ff mov %r9d,-0xb0(%rbp)
2a:* 64 48 8b 04 25 28 00 mov %fs:0x28,%rax <-- trapping instruction
31: 00 00
33: 48 89 45 c8 mov %rax,-0x38(%rbp)
37: 31 c0 xor %eax,%eax
39: 48 rex.W
3a: c7 .byte 0xc7
3b: 85 70 ff test %esi,-0x1(%rax)
3e: ff (bad)
3f: ff .byte 0xff
Code starting with the faulting instruction
===========================================
0: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax
7: 00 00
9: 48 89 45 c8 mov %rax,-0x38(%rbp)
d: 31 c0 xor %eax,%eax
f: 48 rex.W
10: c7 .byte 0xc7
11: 85 70 ff test %esi,-0x1(%rax)
14: ff (bad)
15: ff .byte 0xff
kern :warn : [ 460.793864] process 'recursion-depth' launched '/tmp/1' with NULL argv: empty string added
user :err : [ 461.202285] fixup_efivarfs failed
user :err : [ 462.541150] /lkp/lkp/src/lib/debug.sh:12: die
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240825/202408251749.7e390194-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-25 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 16:56 [PATCH v2] selftests: fix relative rpath usage Eugene Syromiatnikov
2024-08-12 23:03 ` Shuah Khan
2024-08-13 16:33 ` Eugene Syromiatnikov
2024-08-14 11:14 ` Shuah Khan
2024-08-14 12:25 ` Eugene Syromiatnikov
2024-08-19 9:33 ` Shuah Khan
2024-08-23 4:04 ` kernel test robot
2024-08-25 9:40 ` kernel test robot [this message]
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=202408251749.7e390194-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=esyr@redhat.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mykolal@fb.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tiwai@suse.com \
--cc=yonghong.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox