From: kernel test robot <oliver.sang@intel.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [mhiramat:topic/fprobe-on-fgraph] [function_graph] f2ed0fd5cc: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
Date: Wed, 17 Jan 2024 22:59:23 +0800 [thread overview]
Message-ID: <202401172200.c8731564-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:at_kernel/trace/trace.c:#run_tracer_selftest" on:
commit: f2ed0fd5cc77ca2ad957569c35e76ef08cf93f54 ("function_graph: Add a new entry handler with parent_ip and ftrace_regs")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git topic/fprobe-on-fgraph
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+------------------------------------------------------+------------+------------+
| | 2d3653c71e | f2ed0fd5cc |
+------------------------------------------------------+------------+------------+
| WARNING:at_kernel/trace/trace.c:#run_tracer_selftest | 0 | 20 |
| EIP:run_tracer_selftest | 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/202401172200.c8731564-oliver.sang@intel.com
[ 5.535374][ T1] Testing tracer function_graph: .. no entries found ..FAILED!
[ 6.645598][ T1] ------------[ cut here ]------------
[ 6.646006][ T1] WARNING: CPU: 0 PID: 1 at kernel/trace/trace.c:2045 run_tracer_selftest+0x256/0x26c
[ 6.646759][ T1] Modules linked in:
[ 6.647062][ T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G T 6.7.0-rc8-00022-gf2ed0fd5cc77 #1
[ 6.647669][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 6.648455][ T1] EIP: run_tracer_selftest+0x256/0x26c
[ 6.648871][ T1] Code: 00 00 66 90 8b 15 ec 97 d3 d4 b9 ff ff ff ff a1 28 98 d3 d4 e8 37 68 ff ff e9 26 fe ff ff c7 04 24 90 d6 8c d4 e8 92 68 f6 ff <0f> 0b b8 ff ff ff ff e9 a7 fe ff ff b8 f4 ff ff ff e9 9d fe ff ff
[ 6.650343][ T1] EAX: 00000007 EBX: d4e33700 ECX: 00000000 EDX: 00000000
[ 6.650884][ T1] ESI: d4e4a8c0 EDI: c101f100 EBP: c138de8c ESP: c138de78
[ 6.651422][ T1] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010246
[ 6.651661][ T1] CR0: 80050033 CR2: ffcb2000 CR3: 14f88000 CR4: 00040690
[ 6.652189][ T1] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 6.652715][ T1] DR6: fffe0ff0 DR7: 00000400
[ 6.653063][ T1] Call Trace:
[ 6.653309][ T1] ? show_regs+0x82/0x90
[ 6.653630][ T1] ? run_tracer_selftest+0x256/0x26c
[ 6.654025][ T1] ? __warn+0x89/0x1bc
[ 6.654333][ T1] ? run_tracer_selftest+0x256/0x26c
[ 6.654733][ T1] ? run_tracer_selftest+0x256/0x26c
[ 6.655128][ T1] ? report_bug+0x1c5/0x23c
[ 6.655467][ T1] ? exc_overflow+0x58/0x58
[ 6.655661][ T1] ? handle_bug+0x28/0x50
[ 6.655984][ T1] ? exc_invalid_op+0x28/0x7c
[ 6.656332][ T1] ? preempt_count_sub+0xc9/0x120
[ 6.656706][ T1] ? preempt_count_add+0x69/0xc8
[ 6.657074][ T1] ? vprintk_emit+0x7a/0x194
[ 6.657418][ T1] ? handle_exception+0x14d/0x14d
[ 6.657794][ T1] ? exc_overflow+0x58/0x58
[ 6.658130][ T1] ? run_tracer_selftest+0x256/0x26c
[ 6.658530][ T1] ? exc_overflow+0x58/0x58
[ 6.658865][ T1] ? run_tracer_selftest+0x256/0x26c
[ 6.659262][ T1] register_tracer+0xe4/0x28c
[ 6.659612][ T1] ? register_trace_event+0xf6/0x180
[ 6.659661][ T1] ? init_graph_tracefs+0x3c/0x3c
[ 6.660036][ T1] init_graph_trace+0x56/0x7c
[ 6.660386][ T1] do_one_initcall+0x70/0x3b8
[ 6.660732][ T1] ? parameq+0x13/0x68
[ 6.661039][ T1] ? parse_args+0x202/0x37c
[ 6.661383][ T1] do_initcalls+0x100/0x228
[ 6.661721][ T1] ? rdinit_setup+0x40/0x40
[ 6.662061][ T1] ? rest_init+0x194/0x194
[ 6.662393][ T1] kernel_init_freeable+0xd3/0x1c4
[ 6.662772][ T1] kernel_init+0x1a/0x1dc
[ 6.663096][ T1] ? schedule_tail+0x60/0x78
[ 6.663439][ T1] ret_from_fork+0x3d/0x48
[ 6.663661][ T1] ? rest_init+0x194/0x194
[ 6.663992][ T1] ret_from_fork_asm+0x12/0x18
[ 6.664348][ T1] entry_INT80_32+0x10d/0x10d
[ 6.664702][ T1] irq event stamp: 2172679
[ 6.665030][ T1] hardirqs last enabled at (2172687): [<d3cf0dfe>] console_unlock+0x11a/0x178
[ 6.665694][ T1] hardirqs last disabled at (2172694): [<d3cf0de5>] console_unlock+0x101/0x178
[ 6.666360][ T1] softirqs last enabled at (2172316): [<d45fad83>] __do_softirq+0x2f3/0x4b4
[ 6.667009][ T1] softirqs last disabled at (2172309): [<d3c17af3>] do_softirq_own_stack+0x37/0x4c
[ 6.667661][ T1] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240117/202401172200.c8731564-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-17 14:59 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=202401172200.c8731564-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--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).