From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, mhiramat@kernel.org, bristot@redhat.com,
jbaron@akamai.com, torvalds@linux-foundation.org,
tglx@linutronix.de, mingo@kernel.org, namit@vmware.com,
hpa@zytor.com, luto@kernel.org, ard.biesheuvel@linaro.org,
jpoimboe@redhat.com, pbonzini@redhat.com,
mathieu.desnoyers@efficios.com, lkp@lists.01.org
Subject: Re: [tracepoint] 01edfaf177: WARNING:at_kernel/static_call.c:#__static_call_update
Date: Fri, 15 May 2020 19:13:13 +0200 [thread overview]
Message-ID: <20200515171313.GG2940@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200513084811.GG17565@shao2-debian>
On Wed, May 13, 2020 at 04:48:11PM +0800, kernel test robot wrote:
> commit: 01edfaf177311fba9941254793431d2044b00fd7 ("[PATCH v4 12/18] tracepoint: Optimize using static_call()")
> url: https://github.com/0day-ci/linux/commits/Peter-Zijlstra/Add-static_call/20200502-045208
*groan*, so I would really rather you grab patches from by git tree than
suck random crap from lkml like this :/
Anyway, I _suspect_ this is fixed in a later patch that initializes
static_call earlier, but I can't tell for sure, because I really
don't know what to do to reproduce this.
> [ 1.990628] WARNING: CPU: 0 PID: 0 at kernel/static_call.c:113 __static_call_update+0x83/0x29c
> [ 1.990660] Modules linked in:
> [ 1.990703] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.7.0-rc3-next-20200501-00012-g01edfaf177311f #1
> [ 1.990742] RIP: 0010:__static_call_update+0x83/0x29c
> [ 1.990781] Code: 4c 89 f2 48 ff 05 d1 9d 83 06 e8 8e 09 d2 ff 48 ff 05 d5 9d 83 06 80 3d 8e a2 83 06 00 0f 85 f3 01 00 00 48 ff 05 c9 9d 83 06 <0f> 0b 48 ff 05 c8 9d 83 06 48 ff 05 c9 9d 83 06 e9 b0 01 00 00 48
> [ 1.990814] RSP: 0000:ffffffff83c07cf8 EFLAGS: 00010002
> [ 1.990850] RAX: 0000000000000000 RBX: ffffffff86682620 RCX: 0000000000000000
> [ 1.990884] RDX: fffffbfff0780f87 RSI: ffffffff83c918c0 RDI: fffffbfff0780f93
> [ 1.990916] RBP: ffffffff812943ec R08: fffffbfff07e3551 R09: fffffbfff07e3551
> [ 1.990950] R10: ffffffff83f1aa87 R11: 0000000000000001 R12: ffffffff83f6f0c0
> [ 1.990982] R13: 00000000ffffffff R14: ffffffff812943ec R15: ffffffff812943ec
> [ 1.991017] FS: 0000000000000000(0000) GS:ffff8881e8000000(0000) knlGS:0000000000000000
> [ 1.991049] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 1.991081] CR2: ffff88823ffff000 CR3: 0000000003c78000 CR4: 00000000000006b0
> [ 1.991119] Call Trace:
> [ 1.991164] ? __SCT__tp_func_sched_waking+0x8/0x8
> [ 1.991202] ? allocate_probes+0x2d/0x4d
> [ 1.991250] ? probe_sched_switch+0x4f/0x4f
> [ 1.991286] ? __SCT__tp_func_sched_waking+0x8/0x8
> [ 1.991331] ? probe_sched_switch+0x4f/0x4f
> [ 1.991366] tracepoint_update_call+0x6d/0x79
> [ 1.991416] tracepoint_probe_register_prio+0x337/0x47f
> [ 1.991499] tracepoint_probe_register+0x16/0x1e
> [ 1.991538] tracing_start_sched_switch+0xc3/0x1ba
> [ 1.991627] tracing_start_cmdline_record+0x11/0x19
> [ 1.991664] trace_printk_start_comm+0x1c/0x24
> [ 1.991725] trace_event_init+0x1b8/0x20a
> [ 1.991775] trace_init+0xc/0x14
> [ 1.991809] start_kernel+0x8ed/0xe78
> [ 1.991862] ? thread_stack_cache_init+0xd/0xd
> [ 1.991905] ? __early_make_pgtable+0x1b9/0x204
> [ 1.991963] ? early_make_pgtable+0x27/0x2f
> [ 1.992000] ? early_idt_handler_common+0x35/0x4c
> [ 1.992131] x86_64_start_reservations+0x42/0x4a
> [ 1.992170] x86_64_start_kernel+0xe1/0xea
> [ 1.992216] secondary_startup_64+0xa4/0xb0
> [ 1.992336] irq event stamp: 0
> [ 1.992371] hardirqs last enabled at (0): [<0000000000000000>] 0x0
> [ 1.992403] hardirqs last disabled at (0): [<0000000000000000>] 0x0
> [ 1.992437] softirqs last enabled at (0): [<0000000000000000>] 0x0
> [ 1.992469] softirqs last disabled at (0): [<0000000000000000>] 0x0
> [ 1.992562] ---[ end trace 15ea566c311b9aea ]---
>
>
> To reproduce:
>
> # build kernel
> cd linux
> cp config-5.7.0-rc3-next-20200501-00012-g01edfaf177311f .config
> make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Because ^ is just not going to happen. And from the provided information
I cannot decipher what it takes to trigger this.
Also, your dmesg had the trace_printk() splat in, and that is certainly
not from these patches.
next prev parent reply other threads:[~2020-05-15 17:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:28 [PATCH v4 00/18] Add static_call() Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 01/18] notifier: Fix broken error handling pattern Peter Zijlstra
2020-05-01 23:35 ` Steven Rostedt
2020-05-01 20:28 ` [PATCH v4 02/18] module: Fix up module_notifier return values Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 03/18] module: Properly propagate MODULE_STATE_COMING failure Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 04/18] jump_label,module: Fix module lifetime for __jump_label_mod_text_reserved Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 05/18] compiler.h: Make __ADDRESSABLE() symbol truly unique Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 06/18] static_call: Add basic static call infrastructure Peter Zijlstra
2020-05-05 21:21 ` Josh Poimboeuf
2020-05-01 20:28 ` [PATCH v4 07/18] static_call: Add inline " Peter Zijlstra
2020-05-05 22:10 ` Josh Poimboeuf
2020-05-06 16:15 ` Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 08/18] static_call: Avoid kprobes on inline static_call()s Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 09/18] x86/static_call: Add out-of-line static call implementation Peter Zijlstra
2020-05-06 16:16 ` Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 10/18] x86/static_call: Add inline static call implementation for x86-64 Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 11/18] static_call: Simple self-test Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 12/18] tracepoint: Optimize using static_call() Peter Zijlstra
2020-05-13 8:48 ` [tracepoint] 01edfaf177: WARNING:at_kernel/static_call.c:#__static_call_update kernel test robot
2020-05-15 17:13 ` Peter Zijlstra [this message]
2020-05-01 20:29 ` [PATCH v4 13/18] x86/alternatives: Teach text_poke_bp() to emulate RET Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 14/18] static_call: Add static_cond_call() Peter Zijlstra
2020-05-02 13:08 ` Rasmus Villemoes
2020-05-03 12:58 ` Peter Zijlstra
2020-05-04 7:20 ` Rasmus Villemoes
2020-05-04 20:14 ` Peter Zijlstra
2020-05-05 7:50 ` Rasmus Villemoes
2020-05-05 9:38 ` Peter Zijlstra
2020-05-05 9:36 ` Peter Zijlstra
2020-05-05 18:13 ` Nick Desaulniers
2020-05-05 18:27 ` Nick Desaulniers
2020-05-05 18:48 ` Linus Torvalds
2020-05-05 19:00 ` Mathieu Desnoyers
2020-05-05 19:57 ` Nick Desaulniers
2020-05-05 20:27 ` Mathieu Desnoyers
2020-05-06 13:55 ` Peter Zijlstra
2020-05-06 14:01 ` Mathieu Desnoyers
2020-05-06 16:18 ` Peter Zijlstra
2020-05-06 13:51 ` Peter Zijlstra
2020-05-06 16:00 ` Peter Zijlstra
2020-05-06 17:16 ` Linus Torvalds
2020-05-06 19:57 ` Andy Lutomirski
2020-05-06 17:24 ` Josh Poimboeuf
2020-05-06 17:58 ` Peter Zijlstra
2020-05-06 18:09 ` Josh Poimboeuf
2020-05-06 18:16 ` Peter Zijlstra
2020-05-08 15:27 ` Peter Zijlstra
2020-05-08 15:47 ` Josh Poimboeuf
2020-05-08 16:17 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 15/18] static_call: Handle tail-calls Peter Zijlstra
2020-05-06 18:10 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 16/18] static_call: Allow early init Peter Zijlstra
2020-05-06 21:15 ` Josh Poimboeuf
2020-05-08 13:31 ` Peter Zijlstra
2020-05-08 14:27 ` Josh Poimboeuf
2020-05-08 15:30 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 17/18] x86/perf, static_call: Optimize x86_pmu methods Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 18/18] objtool: Clean up elf_write() condition Peter Zijlstra
2020-05-06 17:32 ` [PATCH v4 00/18] Add static_call() Josh Poimboeuf
2020-05-06 18:05 ` Peter Zijlstra
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=20200515171313.GG2940@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bristot@redhat.com \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=pbonzini@redhat.com \
--cc=rong.a.chen@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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