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