From: Steven Rostedt <rostedt@goodmis.org>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG?] perf_event_open fails on synthetic event created through dynamic_events
Date: Mon, 12 May 2025 10:22:22 -0400 [thread overview]
Message-ID: <20250512102222.2361a57a@gandalf.local.home> (raw)
In-Reply-To: <CAP4=nvS2r=-1GgnmsEA9s7JPs1EVg9R63FLLNboN=f1cq0WEqQ@mail.gmail.com>
On Mon, 12 May 2025 16:08:42 +0200
Tomas Glozar <tglozar@redhat.com> wrote:
> It seems that it is trying to access a struct tracepoint object whose
> func field is NULL. I have not tried attaching to dynamic events
> through perf before, so I don't know whether this is just
> unimplemented and poorly handled or a regression. For what it's worth,
> it also happens on CentOS Stream 9 kernel (5.14.0-578.el9).
I think it is unimplemented and poorly handled ;-)
If this is something you want, we can add the feature for it, but for this
release and stable kernels, as it's not a regression, the fix is to have it
not produce a warning and give something like "-EINVAL" back to the perf
system call.
-- Steve
prev parent reply other threads:[~2025-05-12 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 14:08 [BUG?] perf_event_open fails on synthetic event created through dynamic_events Tomas Glozar
2025-05-12 14:22 ` Steven Rostedt [this message]
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=20250512102222.2361a57a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglozar@redhat.com \
/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 NNTP newsgroup(s).