From: kernel test robot <oliver.sang@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [viro-vfs:work.fdtable] 2b6b3f37af: segfault_at_ip_sp_error
Date: Mon, 7 Oct 2024 21:31:20 +0800 [thread overview]
Message-ID: <202410072137.2c3cf4d2-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "segfault_at_ip_sp_error" on:
commit: 2b6b3f37af99157303aae84beef05719b9c1ae25 ("make __set_open_fd() set cloexec state as well")
https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git work.fdtable
in testcase: boot
compiler: clang-18
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-------------------------+------------+------------+
| | fecbd3b1c4 | 2b6b3f37af |
+-------------------------+------------+------------+
| segfault_at_ip_sp_error | 0 | 30 |
+-------------------------+------------+------------+
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/202410072137.2c3cf4d2-oliver.sang@intel.com
[ 7.803982][ T1] init: mountall-shell main process (1527) terminated with status 1
[ 7.824097][ T1] init: Error while reading from descriptor: Bad file descriptor
[ 7.825777][ T1] init: mountall-shell post-stop process (1531) terminated with status 1
LKP: ttyS0: 1523: skip deploy intel ucode as no ucode is specified
LKP: ttyS0: 1523: Kernel tests: Boot OK!
[ 7.928802][ T1540] sed[1540]: segfault at 0 ip 00007ff78f062ca0 sp 00007fffc9fc24f8 error 4 in libc-2.15.so[71ca0,7ff78eff1000+1b3000] likely on CPU 0 (core 0, socket 0)
LKP: ttyS0: 1523: HOSTNAME vm-snb, MAC 6e:6f:1b:a7:2f:20, kernel 6.12.0-rc1-00011-g2b6b3f37af99 1
[ 7.931951][ T1540] Code: e8 25 e5 08 00 48 81 c4 80 00 00 00 eb 84 48 8d 3a 48 81 ec 80 00 00 00 e8 3d e5 08 00 48 81 c4 80 00 00 00 eb b4 90 90 90 90 <8b> 0f 31 f6 49 89 f8 f6 c1 20 89 c8 40 0f 95 c6 25 00 80 00 00 75
All code
========
0: e8 25 e5 08 00 callq 0x8e52a
5: 48 81 c4 80 00 00 00 add $0x80,%rsp
c: eb 84 jmp 0xffffffffffffff92
e: 48 8d 3a lea (%rdx),%rdi
11: 48 81 ec 80 00 00 00 sub $0x80,%rsp
18: e8 3d e5 08 00 callq 0x8e55a
1d: 48 81 c4 80 00 00 00 add $0x80,%rsp
24: eb b4 jmp 0xffffffffffffffda
26: 90 nop
27: 90 nop
28: 90 nop
29: 90 nop
2a:* 8b 0f mov (%rdi),%ecx <-- trapping instruction
2c: 31 f6 xor %esi,%esi
2e: 49 89 f8 mov %rdi,%r8
31: f6 c1 20 test $0x20,%cl
34: 89 c8 mov %ecx,%eax
36: 40 0f 95 c6 setne %sil
3a: 25 00 80 00 00 and $0x8000,%eax
3f: 75 .byte 0x75
Code starting with the faulting instruction
===========================================
0: 8b 0f mov (%rdi),%ecx
2: 31 f6 xor %esi,%esi
4: 49 89 f8 mov %rdi,%r8
7: f6 c1 20 test $0x20,%cl
a: 89 c8 mov %ecx,%eax
c: 40 0f 95 c6 setne %sil
10: 25 00 80 00 00 and $0x8000,%eax
15: 75 .byte 0x75
[ 7.946359][ T1542] sed[1542]: segfault at 0 ip 00007f3e8dad5ca0 sp 00007ffdac63ab68 error 4 likely on CPU 1 (core 1, socket 0)
[ 7.948095][ T1542] Code: e8 25 e5 08 00 48 81 c4 80 00 00 00 eb 84 48 8d 3a 48 81 ec 80 00 00 00 e8 3d e5 08 00 48 81 c4 80 00 00 00 eb b4 90 90 90 90 <8b> 0f 31 f6 49 89 f8 f6 c1 20 89 c8 40 0f 95 c6 25 00 80 00 00 75
All code
========
0: e8 25 e5 08 00 callq 0x8e52a
5: 48 81 c4 80 00 00 00 add $0x80,%rsp
c: eb 84 jmp 0xffffffffffffff92
e: 48 8d 3a lea (%rdx),%rdi
11: 48 81 ec 80 00 00 00 sub $0x80,%rsp
18: e8 3d e5 08 00 callq 0x8e55a
1d: 48 81 c4 80 00 00 00 add $0x80,%rsp
24: eb b4 jmp 0xffffffffffffffda
26: 90 nop
27: 90 nop
28: 90 nop
29: 90 nop
2a:* 8b 0f mov (%rdi),%ecx <-- trapping instruction
2c: 31 f6 xor %esi,%esi
2e: 49 89 f8 mov %rdi,%r8
31: f6 c1 20 test $0x20,%cl
34: 89 c8 mov %ecx,%eax
36: 40 0f 95 c6 setne %sil
3a: 25 00 80 00 00 and $0x8000,%eax
3f: 75 .byte 0x75
Code starting with the faulting instruction
===========================================
0: 8b 0f mov (%rdi),%ecx
2: 31 f6 xor %esi,%esi
4: 49 89 f8 mov %rdi,%r8
7: f6 c1 20 test $0x20,%cl
a: 89 c8 mov %ecx,%eax
c: 40 0f 95 c6 setne %sil
10: 25 00 80 00 00 and $0x8000,%eax
15: 75 .byte 0x75
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241007/202410072137.2c3cf4d2-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-07 13:31 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=202410072137.2c3cf4d2-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).