Steven Rostedt
6819bc6285
tracing: Do not register unsupported perf events
commit ef7f38df89 upstream.
Synthetic events currently do not have a function to register perf events.
This leads to calling the tracepoint register functions with a NULL
function pointer which triggers:
------------[ cut here ]------------
WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272
Modules linked in: kvm_intel kvm irqbypass
CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014
RIP: 0010:tracepoint_add_func+0x357/0x370
Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc <0f> 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f
RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246
RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000
RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8
RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780
R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a
R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78
FS: 00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0
Call Trace:
<TASK>
tracepoint_probe_register+0x5d/0x90
synth_event_reg+0x3c/0x60
perf_trace_event_init+0x204/0x340
perf_trace_init+0x85/0xd0
perf_tp_event_init+0x2e/0x50
perf_try_init_event+0x6f/0x230
? perf_event_alloc+0x4bb/0xdc0
perf_event_alloc+0x65a/0xdc0
__se_sys_perf_event_open+0x290/0x9f0
do_syscall_64+0x93/0x7b0
? entry_SYSCALL_64_after_hwframe+0x76/0x7e
? trace_hardirqs_off+0x53/0xc0
entry_SYSCALL_64_after_hwframe+0x76/0x7e
Instead, have the code return -ENODEV, which doesn't warn and has perf
error out with:
# perf record -e synthetic:futex_wait
Error:
The sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).
"dmesg | grep -i perf" may provide additional information.
Ideally perf should support synthetic events, but for now just fix the
warning. The support can come later.
Cc: stable@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: https://patch.msgid.link/20251216182440.147e4453@gandalf.local.home
Fixes: 4b147936fa ("tracing: Add support for 'synthetic' events")
Reported-by: Ian Rogers <irogers@google.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2026-01-19 13:11:51 +01:00
..
2023-01-14 10:15:41 +01:00
2025-06-27 11:04:03 +01:00
2020-07-13 16:55:49 -07:00
2021-02-10 09:29:16 +01:00
2020-05-12 18:24:34 -04:00
2025-08-28 16:22:52 +02:00
2024-07-05 09:12:37 +02:00
2023-04-05 11:23:46 +02:00
2020-08-09 14:10:26 -07:00
2025-10-29 14:01:16 +01:00
2020-07-29 11:43:53 +02:00
2025-04-10 14:30:59 +02:00
2024-01-05 15:12:28 +01:00
2021-09-22 12:28:03 +02:00
2024-12-14 19:48:30 +01:00
2025-10-02 13:35:47 +02:00
2020-06-16 21:21:02 -04:00
2024-12-14 19:47:57 +01:00
2025-05-02 07:41:02 +02:00
2025-12-07 06:08:16 +09:00
2023-10-10 21:53:25 +02:00
2025-12-07 06:08:08 +09:00
2024-05-02 16:23:36 +02:00
2026-01-19 13:11:51 +01:00
2020-10-25 14:51:49 -07:00
2025-04-10 14:31:02 +02:00
2021-10-27 09:56:56 +02:00
2020-11-30 21:43:07 -05:00
2025-04-10 14:31:02 +02:00
2025-10-29 14:01:13 +01:00
2024-10-17 15:08:28 +02:00
2022-09-23 14:16:58 +02:00
2020-10-15 15:51:28 -07:00
2023-08-26 15:26:50 +02:00
2024-11-08 16:21:59 +01:00
2025-10-29 14:01:13 +01:00
2025-04-10 14:31:02 +02:00
2020-12-30 11:54:28 +01:00
2020-09-18 22:17:14 -04:00
2020-09-18 22:17:14 -04:00
2025-05-02 07:41:10 +02:00
2025-10-29 14:01:13 +01:00
2025-10-02 13:35:36 +02:00
2025-08-28 16:22:58 +02:00
2024-12-14 19:48:22 +01:00