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
..
2025-12-07 06:08:07 +09:00
2025-10-02 13:35:40 +02:00
2025-03-13 12:47:22 +01:00
2026-01-19 13:11:38 +01:00
2023-01-04 11:39:22 +01:00
2025-12-07 06:08:10 +09:00
2023-11-20 11:06:44 +01:00
2025-12-07 06:08:19 +09:00
2025-10-02 13:35:39 +02:00
2024-12-14 19:48:25 +01:00
2026-01-19 13:11:41 +01:00
2026-01-19 13:11:25 +01:00
2025-08-28 16:22:41 +02:00
2025-03-13 12:47:01 +01:00
2025-08-28 16:22:42 +02:00
2025-10-29 14:01:20 +01:00
2025-06-27 11:04:15 +01:00
2026-01-19 13:11:51 +01:00
2021-05-11 14:47:37 +02:00
2025-03-13 12:47:35 +01:00
2024-02-23 08:41:53 +01:00
2024-06-21 14:53:39 +02:00
2024-06-21 14:53:39 +02:00
2024-06-21 14:53:39 +02:00
2024-02-23 08:42:03 +01:00
2022-04-08 14:40:00 +02:00
2024-07-18 13:05:44 +02:00
2023-09-19 12:20:13 +02:00
2020-07-30 11:15:58 -07:00
2024-05-02 16:23:46 +02:00
2020-10-13 09:17:34 -07:00
2023-04-05 11:23:45 +02:00
2021-09-15 09:50:40 +02:00
2025-02-01 18:22:29 +01:00
2021-06-23 14:42:52 +02:00
2023-12-20 15:44:30 +01:00
2025-06-27 11:04:24 +01:00
2023-03-11 16:40:18 +01:00
2025-10-29 14:01:11 +01:00
2021-04-07 15:00:14 +02:00
2025-02-01 18:22:28 +01:00
2020-10-13 09:17:34 -07:00
2020-11-02 12:14:19 -08:00
2021-07-20 16:05:58 +02:00
2024-10-17 15:08:29 +02:00
2024-06-21 14:52:48 +02:00
2024-07-05 09:12:41 +02:00
2023-07-27 08:43:40 +02:00
2025-04-10 14:30:58 +02:00
2023-06-21 15:45:37 +02:00
2023-04-20 12:10:29 +02:00
2023-04-20 12:10:29 +02:00
2023-05-17 11:47:33 +02:00
2020-08-12 10:58:01 -07:00
2024-10-17 15:07:37 +02:00
2023-04-20 12:10:29 +02:00
2024-10-17 15:07:50 +02:00
2023-01-14 10:15:20 +01:00
2021-03-25 09:04:11 +01:00
2021-03-25 09:04:11 +01:00
2024-10-17 15:08:29 +02:00
2020-09-01 09:58:03 +02:00
2025-10-29 14:01:23 +01:00
2024-04-13 12:59:40 +02:00
2025-06-04 14:36:55 +02:00
2024-07-05 09:12:33 +02:00
2025-10-29 14:01:14 +01:00
2025-01-09 13:25:04 +01:00
2022-06-09 10:20:49 +02:00
2020-10-16 11:11:19 -07:00
2023-11-28 16:54:58 +00:00
2020-07-27 14:31:12 -04:00
2023-05-17 11:47:34 +02:00
2025-05-02 07:41:09 +02:00
2025-07-17 18:28:01 +02:00
2023-09-23 11:01:05 +02:00
2026-01-19 13:11:50 +01:00
2024-03-01 13:16:46 +01:00
2024-10-17 15:08:12 +02:00
2024-09-12 11:06:48 +02:00
2021-07-14 16:55:50 +02:00
2020-09-16 15:18:56 +02:00
2022-02-23 12:01:00 +01:00
2020-09-18 14:24:16 +01:00
2024-12-19 18:06:13 +01:00
2020-10-26 12:12:27 +01:00
2024-07-05 09:12:55 +02:00
2024-06-21 14:52:58 +02:00
2024-06-21 14:53:18 +02:00
2024-08-19 05:40:57 +02:00
2020-10-02 19:11:12 -07:00
2023-08-30 16:23:17 +02:00
2021-09-03 10:09:30 +02:00
2022-01-27 10:54:33 +01:00
2024-06-21 14:53:06 +02:00
2020-10-06 10:31:52 -07:00
2021-05-14 09:50:46 +02:00
2021-09-08 08:49:00 +02:00
2021-03-30 14:32:03 +02:00
2025-04-10 14:30:55 +02:00
2024-08-19 05:41:01 +02:00
2023-11-28 16:54:56 +00:00
2023-12-08 08:46:13 +01:00