From: kernel test robot <oliver.sang@intel.com>
To: <kernel@openeuler.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [openeuler:OLK-6.6] f04c0f3eb9: WARNING:at_kernel/events/core.c:#__se_sys_perf_event_open
Date: Fri, 22 Mar 2024 16:58:13 +0800 [thread overview]
Message-ID: <202403221606.ef6e1314-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:at_kernel/events/core.c:#__se_sys_perf_event_open" on:
commit: f04c0f3eb9b49427c273cd3e4d5a2ff895855b4b ("make OPTIMIZE_INLINING config editable")
https://gitee.com/openeuler/kernel.git OLK-6.6
in testcase: kernel-selftests
version: kernel-selftests-x86_64-4306b286-1_20240301
with following parameters:
group: kvm
compiler: gcc-12
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed there is config diff for the build of this commit comparing to
its parent:
==================== PARENT FIRST_BAD KCONFIGS 56cf5545eddd8cebeb2eed8f7c1b6727d59a529a ====================
--- /pkg/linux/x86_64-openeuler_defconfig-OLK-6.6-kselftests/gcc-12/56cf5545eddd8cebeb2eed8f7c1b6727d59a529a/.config 2024-03-17 05:06:25.898486325 +0800
+++ /pkg/linux/x86_64-openeuler_defconfig-OLK-6.6-kselftests/gcc-12/f04c0f3eb9b49427c273cd3e4d5a2ff895855b4b/.config 2024-03-16 00:01:36.829873758 +0800
@@ -9245,7 +9245,7 @@ CONFIG_FRAME_WARN=2048
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_READABLE_ASM is not set
# CONFIG_HEADERS_INSTALL is not set
-CONFIG_OPTIMIZE_INLINING=y
+# CONFIG_OPTIMIZE_INLINING is not set
CONFIG_DEBUG_SECTION_MISMATCH=y
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_FUNCTION_ALIGN_64B is not set
we also noticed there is another warning for parent in this test:
56cf5545eddd8ceb f04c0f3eb9b49427c273cd3e4d5
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
6:6 -83% :6 dmesg.WARNING:at_kernel/events/core.c:#__do_sys_perf_event_open
:6 100% 6:6 dmesg.WARNING:at_kernel/events/core.c:#__se_sys_perf_event_open
we are not sure if they are just same issue and if the difference is caused by
config diff. just report what we observed in our tests FYI.
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/202403221606.ef6e1314-oliver.sang@intel.com
kern :warn : [ 101.829579] ------------[ cut here ]------------
kern :warn : [ 101.837366] WARNING: CPU: 31 PID: 3360 at kernel/events/core.c:1950 __se_sys_perf_event_open (kernel/events/core.c:1950 kernel/events/core.c:12643 kernel/events/core.c:12376)
kern :warn : [ 101.850445] Modules linked in: intel_rapl_msr intel_rapl_common intel_ifs i10nm_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp btrfs kvm_intel xor kvm raid6_pq libcrc32c irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 nvme snd_pcm snd_timer nvme_core dax_hmem snd ast t10_pi ipmi_ssif cxl_acpi rapl soundcore drm_shmem_helper intel_cstate cxl_core isst_if_mmio pcspkr isst_if_mbox_pci mei_me crc64_rocksoft_generic idxd crc64_rocksoft isst_if_common i2c_i801 idxd_bus cdc_ether drm_kms_helper crc64 mei i2c_smbus i2c_ismt wmi acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler pinctrl_emmitsburg acpi_pad acpi_power_meter joydev binfmt_misc fuse loop drm dm_mod ip_tables
kern :warn : [ 101.928047] CPU: 31 PID: 3360 Comm: ovsdb-server Not tainted 6.6.0-02358-gf04c0f3eb9b4 #1
kern :warn : [ 101.939446] RIP: 0010:__se_sys_perf_event_open (kernel/events/core.c:1950 kernel/events/core.c:12643 kernel/events/core.c:12376)
kern :warn : [ 101.947893] Code: 44 49 8b 86 28 02 00 00 83 ce ff 4c 89 54 24 38 48 8d b8 a8 00 00 00 e8 48 fd 5e 02 4c 8b 54 24 38 83 e8 01 0f 84 4b f4 ff ff <0f> 0b e9 44 f4 ff ff 4c 89 54 24 38 e8 e9 d4 26 00 4c 8b 54 24 38
All code
========
0: 44 rex.R
1: 49 8b 86 28 02 00 00 mov 0x228(%r14),%rax
8: 83 ce ff or $0xffffffff,%esi
b: 4c 89 54 24 38 mov %r10,0x38(%rsp)
10: 48 8d b8 a8 00 00 00 lea 0xa8(%rax),%rdi
17: e8 48 fd 5e 02 call 0x25efd64
1c: 4c 8b 54 24 38 mov 0x38(%rsp),%r10
21: 83 e8 01 sub $0x1,%eax
24: 0f 84 4b f4 ff ff je 0xfffffffffffff475
2a:* 0f 0b ud2 <-- trapping instruction
2c: e9 44 f4 ff ff jmp 0xfffffffffffff475
31: 4c 89 54 24 38 mov %r10,0x38(%rsp)
36: e8 e9 d4 26 00 call 0x26d524
3b: 4c 8b 54 24 38 mov 0x38(%rsp),%r10
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: e9 44 f4 ff ff jmp 0xfffffffffffff44b
7: 4c 89 54 24 38 mov %r10,0x38(%rsp)
c: e8 e9 d4 26 00 call 0x26d4fa
11: 4c 8b 54 24 38 mov 0x38(%rsp),%r10
kern :warn : [ 101.971209] RSP: 0018:ffa000001fa17ca0 EFLAGS: 00010297
kern :warn : [ 101.979348] RAX: 00000000ffffffff RBX: ff110001c78b8800 RCX: 0000000000000000
kern :warn : [ 101.989724] RDX: 0000000000000000 RSI: 00000000000000a8 RDI: ff110004e4b10ee8
kern :warn : [ 101.999912] RBP: ff110004e4b10040 R08: 0000000000000001 R09: fffffbfff0e4038e
kern :warn : [ 102.010156] R10: 0000000000000000 R11: ffffffff86d9fb60 R12: ff1100010970bdc8
kern :warn : [ 102.020466] R13: 0000000000000002 R14: ff1100010970bdc8 R15: 1ff4000003f42f9d
kern :warn : [ 102.030576] FS: 00007fe9bd77ea00(0000) GS:ff110017fd780000(0000) knlGS:0000000000000000
kern :warn : [ 102.041834] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kern :warn : [ 102.050606] CR2: 0000560e77e04148 CR3: 00000004e4a18006 CR4: 0000000000f71ee0
kern :warn : [ 102.060770] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kern :warn : [ 102.070958] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
kern :warn : [ 102.081205] PKRU: 55555554
kern :warn : [ 102.086508] Call Trace:
kern :warn : [ 102.091509] <TASK>
kern :warn : [ 102.095979] ? __warn (kernel/panic.c:673)
kern :warn : [ 102.101695] ? __se_sys_perf_event_open (kernel/events/core.c:1950 kernel/events/core.c:12643 kernel/events/core.c:12376)
kern :warn : [ 102.109641] ? report_bug (lib/bug.c:180 lib/bug.c:219)
kern :warn : [ 102.115872] ? handle_bug (arch/x86/kernel/traps.c:242)
kern :warn : [ 102.121861] ? exc_invalid_op (arch/x86/kernel/traps.c:263 (discriminator 1))
kern :warn : [ 102.128369] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:568)
kern :warn : [ 102.135276] ? __se_sys_perf_event_open (kernel/events/core.c:1950 kernel/events/core.c:12643 kernel/events/core.c:12376)
kern :warn : [ 102.143105] ? perf_event_set_output (kernel/events/core.c:12376)
kern :warn : [ 102.150553] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4566)
kern :warn : [ 102.159201] do_syscall_64 (arch/x86/entry/common.c:51 arch/x86/entry/common.c:81)
kern :warn : [ 102.165447] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)
kern :warn : [ 102.173312] RIP: 0033:0x7fe9bda2d719
kern :warn : [ 102.179574] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 06 0d 00 f7 d8 64 89 01 48
All code
========
0: 08 89 e8 5b 5d c3 or %cl,-0x3ca2a418(%rcx)
6: 66 2e 0f 1f 84 00 00 cs nopw 0x0(%rax,%rax,1)
d: 00 00 00
10: 90 nop
11: 48 89 f8 mov %rdi,%rax
14: 48 89 f7 mov %rsi,%rdi
17: 48 89 d6 mov %rdx,%rsi
1a: 48 89 ca mov %rcx,%rdx
1d: 4d 89 c2 mov %r8,%r10
20: 4d 89 c8 mov %r9,%r8
23: 4c 8b 4c 24 08 mov 0x8(%rsp),%r9
28: 0f 05 syscall
2a:* 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax <-- trapping instruction
30: 73 01 jae 0x33
32: c3 ret
33: 48 8b 0d b7 06 0d 00 mov 0xd06b7(%rip),%rcx # 0xd06f1
3a: f7 d8 neg %eax
3c: 64 89 01 mov %eax,%fs:(%rcx)
3f: 48 rex.W
Code starting with the faulting instruction
===========================================
0: 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax
6: 73 01 jae 0x9
8: c3 ret
9: 48 8b 0d b7 06 0d 00 mov 0xd06b7(%rip),%rcx # 0xd06c7
10: f7 d8 neg %eax
12: 64 89 01 mov %eax,%fs:(%rcx)
15: 48 rex.W
kern :warn : [ 102.202805] RSP: 002b:00007fffe75bf638 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
kern :warn : [ 102.213627] RAX: ffffffffffffffda RBX: 00007fffe75bf840 RCX: 00007fe9bda2d719
kern :warn : [ 102.223757] RDX: 00000000ffffffff RSI: 0000000000000000 RDI: 00007fffe75bf640
kern :warn : [ 102.233930] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000008000000000
kern :warn : [ 102.244158] R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fffe75bf820
kern :warn : [ 102.254432] R13: 0000560e77df57c0 R14: 0000560e79a93b10 R15: 0000000000000000
kern :warn : [ 102.264524] </TASK>
kern :warn : [ 102.269182] irq event stamp: 10473
kern :warn : [ 102.275213] hardirqs last enabled at (10487): console_unlock (arch/x86/include/asm/irqflags.h:42 arch/x86/include/asm/irqflags.h:77 arch/x86/include/asm/irqflags.h:135 kernel/printk/printk.c:347 kernel/printk/printk.c:2718 kernel/printk/printk.c:3037)
kern :warn : [ 102.287149] hardirqs last disabled at (10500): console_unlock (kernel/printk/printk.c:345 kernel/printk/printk.c:2718 kernel/printk/printk.c:3037)
kern :warn : [ 102.299013] softirqs last enabled at (10424): __do_softirq (arch/x86/include/asm/preempt.h:27 kernel/softirq.c:400 kernel/softirq.c:582)
kern :warn : [ 102.310645] softirqs last disabled at (10523): irq_exit_rcu (kernel/softirq.c:427 kernel/softirq.c:632 kernel/softirq.c:644)
kern :warn : [ 102.322451] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240322/202403221606.ef6e1314-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-22 8:58 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=202403221606.ef6e1314-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=kernel@openeuler.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).