From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] fgraph: Keep track of when fgraph_ops are registered or not
Date: Thu, 19 Jun 2025 12:45:17 +0900 [thread overview]
Message-ID: <20250619124517.3e6665439e1794918e83f1b6@kernel.org> (raw)
In-Reply-To: <20250618073117.024efb2e@gandalf.local.home>
On Wed, 18 Jun 2025 07:31:17 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> Add a warning if unregister_ftrace_graph() is called without ever
> registering it, or if register_ftrace_graph() is called twice. This can
> detect errors when they happen and not later when there's a side effect:
>
> Link: https://lore.kernel.org/all/20250617120830.24fbdd62@gandalf.local.home/
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/fgraph.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/fgraph.c b/kernel/trace/fgraph.c
> index c5b207992fb4..c6bb6c68764f 100644
> --- a/kernel/trace/fgraph.c
> +++ b/kernel/trace/fgraph.c
> @@ -1325,6 +1325,10 @@ int register_ftrace_graph(struct fgraph_ops *gops)
> int ret = 0;
> int i = -1;
>
> + if (WARN_ONCE(gops->ops.flags & FTRACE_OPS_FL_GRAPH,
> + "function graph ops registered again"))
> + return -EBUSY;
> +
> guard(mutex)(&ftrace_lock);
>
> if (!fgraph_stack_cachep) {
> @@ -1401,17 +1405,21 @@ void unregister_ftrace_graph(struct fgraph_ops *gops)
> {
> int command = 0;
>
> + if (WARN_ONCE(!(gops->ops.flags & FTRACE_OPS_FL_GRAPH),
> + "function graph ops unregistered without registering"))
> + return;
> +
> guard(mutex)(&ftrace_lock);
>
> if (unlikely(!ftrace_graph_active))
> - return;
> + goto out;
>
> if (unlikely(gops->idx < 0 || gops->idx >= FGRAPH_ARRAY_SIZE ||
> fgraph_array[gops->idx] != gops))
> - return;
> + goto out;
>
> if (fgraph_lru_release_index(gops->idx) < 0)
> - return;
> + goto out;
>
> fgraph_array[gops->idx] = &fgraph_stub;
>
> @@ -1434,4 +1442,6 @@ void unregister_ftrace_graph(struct fgraph_ops *gops)
> unregister_trace_sched_switch(ftrace_graph_probe_sched_switch, NULL);
> }
> gops->saved_func = NULL;
> + out:
> + gops->ops.flags = 0;
Can we make it cleaning only FTRACE_OPS_FL_GRAPH flag here?
Or, ops.flags should be set again before registering it?
Thank you,
> }
> --
> 2.47.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-06-19 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 11:31 Steven Rostedt
2025-06-19 3:45 ` Masami Hiramatsu [this message]
2025-07-01 22:28 ` Steven Rostedt
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=20250619124517.3e6665439e1794918e83f1b6@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®