From: Steven Rostedt <rostedt@goodmis.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] function_graph: remove unnecessary initialization in ftrace_graph_ret_addr()
Date: Mon, 16 Sep 2024 12:39:25 -0400 [thread overview]
Message-ID: <20240916123925.5398abdf@rorschach.local.home> (raw)
In-Reply-To: <20240916135643.GA23958@redhat.com>
On Mon, 16 Sep 2024 15:56:43 +0200
Oleg Nesterov <oleg@redhat.com> wrote:
> After the commit 29c1c24a2707 ("function_graph: Fix up ftrace_graph_ret_addr()")
> ftrace_graph_ret_addr() doesn't need to initialize "int i" at the start.
>
> While at it, move the declaration of "ret_stack" into the main loop.
Should not make two changes like this, because it risks the entire
patch being denied.
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> kernel/trace/fgraph.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/fgraph.c b/kernel/trace/fgraph.c
> index d7d4fb403f6f..d45a8bc97997 100644
> --- a/kernel/trace/fgraph.c
> +++ b/kernel/trace/fgraph.c
> @@ -890,9 +890,8 @@ ftrace_graph_get_ret_stack(struct task_struct *task, int idx)
> unsigned long ftrace_graph_ret_addr(struct task_struct *task, int *idx,
> unsigned long ret, unsigned long *retp)
> {
> - struct ftrace_ret_stack *ret_stack;
> unsigned long return_handler = (unsigned long)dereference_kernel_function_descriptor(return_to_handler);
> - int i = task->curr_ret_stack;
> + int i;
I'm fine with removing the unneeded init of i.
>
> if (ret != return_handler)
> return ret;
> @@ -902,7 +901,7 @@ unsigned long ftrace_graph_ret_addr(struct task_struct *task, int *idx,
>
> i = *idx ? : task->curr_ret_stack;
> while (i > 0) {
> - ret_stack = get_ret_stack(task, i, &i);
> + struct ftrace_ret_stack *ret_stack = get_ret_stack(task, i, &i);
This is just a preference. Sometimes I like the declaration up on top,
sometimes in the block it used. But this case, I wont it at top.
Please make a v2 with just the change to i.
-- Steve
> if (!ret_stack)
> break;
> /*
next prev parent reply other threads:[~2024-09-16 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 13:56 Oleg Nesterov
2024-09-16 16:39 ` Steven Rostedt [this message]
2024-09-16 17:58 ` [PATCH v2] " Oleg Nesterov
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=20240916123925.5398abdf@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=puranjay@kernel.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®