From: kernel test robot <oliver.sang@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [axboe-block:rw_iter] [fs/proc] 611088cbf6: segfault_at_ip_sp_error
Date: Mon, 22 Apr 2024 14:55:30 +0800 [thread overview]
Message-ID: <202404221436.c921df08-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "segfault_at_ip_sp_error" on:
commit: 611088cbf6bda5c9218c735809215f2b6f6ca8a9 ("fs/proc: convert to read/write iterators")
https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git rw_iter
in testcase: boot
compiler: gcc-13
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--------------------------------------------------------------+------------+------------+
| | 255806aeec | 611088cbf6 |
+--------------------------------------------------------------+------------+------------+
| segfault_at_ip_sp_error | 0 | 20 |
+--------------------------------------------------------------+------------+------------+
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/202404221436.c921df08-oliver.sang@intel.com
[ 809.068720][ T602] vmstat[602]: segfault at 50b000 ip b7f2f6ec sp bfef7790 error 6 in libprocps.so.7.1.0[b7f2f000+a000] likely on CPU 0 (core 0, socket 0)
[ 809.071867][ T602] Code: 84 91 00 00 00 89 74 24 0c 89 ee 89 cd 90 57 6a 01 6a 08 55 e8 e5 fb ff ff 8b 83 f0 09 00 00 8b 54 24 24 8b 4c 24 28 83 c4 10 <89> 14 30 89 4c 30 04 8b 44 24 14 83 c6 08 85 c0 75 d2 8b 74 24 0c
All code
========
0: 84 91 00 00 00 89 test %dl,-0x77000000(%rcx)
6: 74 24 je 0x2c
8: 0c 89 or $0x89,%al
a: ee out %al,(%dx)
b: 89 cd mov %ecx,%ebp
d: 90 nop
e: 57 push %rdi
f: 6a 01 pushq $0x1
11: 6a 08 pushq $0x8
13: 55 push %rbp
14: e8 e5 fb ff ff callq 0xfffffffffffffbfe
19: 8b 83 f0 09 00 00 mov 0x9f0(%rbx),%eax
1f: 8b 54 24 24 mov 0x24(%rsp),%edx
23: 8b 4c 24 28 mov 0x28(%rsp),%ecx
27: 83 c4 10 add $0x10,%esp
2a:* 89 14 30 mov %edx,(%rax,%rsi,1) <-- trapping instruction
2d: 89 4c 30 04 mov %ecx,0x4(%rax,%rsi,1)
31: 8b 44 24 14 mov 0x14(%rsp),%eax
35: 83 c6 08 add $0x8,%esi
38: 85 c0 test %eax,%eax
3a: 75 d2 jne 0xe
3c: 8b 74 24 0c mov 0xc(%rsp),%esi
Code starting with the faulting instruction
===========================================
0: 89 14 30 mov %edx,(%rax,%rsi,1)
3: 89 4c 30 04 mov %ecx,0x4(%rax,%rsi,1)
7: 8b 44 24 14 mov 0x14(%rsp),%eax
b: 83 c6 08 add $0x8,%esi
e: 85 c0 test %eax,%eax
10: 75 d2 jne 0xffffffffffffffe4
12: 8b 74 24 0c mov 0xc(%rsp),%esi
[ 809.127897][ T543] vmstat[543]: segfault at 4df000 ip b7f926ec sp bfe31560 error 6 in libprocps.so.7.1.0[b7f92000+a000] likely on CPU 0 (core 0, socket 0)
[ 809.131027][ T543] Code: 84 91 00 00 00 89 74 24 0c 89 ee 89 cd 90 57 6a 01 6a 08 55 e8 e5 fb ff ff 8b 83 f0 09 00 00 8b 54 24 24 8b 4c 24 28 83 c4 10 <89> 14 30 89 4c 30 04 8b 44 24 14 83 c6 08 85 c0 75 d2 8b 74 24 0c
All code
========
0: 84 91 00 00 00 89 test %dl,-0x77000000(%rcx)
6: 74 24 je 0x2c
8: 0c 89 or $0x89,%al
a: ee out %al,(%dx)
b: 89 cd mov %ecx,%ebp
d: 90 nop
e: 57 push %rdi
f: 6a 01 pushq $0x1
11: 6a 08 pushq $0x8
13: 55 push %rbp
14: e8 e5 fb ff ff callq 0xfffffffffffffbfe
19: 8b 83 f0 09 00 00 mov 0x9f0(%rbx),%eax
1f: 8b 54 24 24 mov 0x24(%rsp),%edx
23: 8b 4c 24 28 mov 0x28(%rsp),%ecx
27: 83 c4 10 add $0x10,%esp
2a:* 89 14 30 mov %edx,(%rax,%rsi,1) <-- trapping instruction
2d: 89 4c 30 04 mov %ecx,0x4(%rax,%rsi,1)
31: 8b 44 24 14 mov 0x14(%rsp),%eax
35: 83 c6 08 add $0x8,%esi
38: 85 c0 test %eax,%eax
3a: 75 d2 jne 0xe
3c: 8b 74 24 0c mov 0xc(%rsp),%esi
Code starting with the faulting instruction
===========================================
0: 89 14 30 mov %edx,(%rax,%rsi,1)
3: 89 4c 30 04 mov %ecx,0x4(%rax,%rsi,1)
7: 8b 44 24 14 mov 0x14(%rsp),%eax
b: 83 c6 08 add $0x8,%esi
e: 85 c0 test %eax,%eax
10: 75 d2 jne 0xffffffffffffffe4
12: 8b 74 24 0c mov 0xc(%rsp),%esi
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240422/202404221436.c921df08-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-22 6:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202404221436.c921df08-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).