From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org,
Menglong Dong <dongml2@chinatelecom.cn>
Subject: Re: [PATCH bpf v2] ftrace: fix incorrect hash size in register_ftrace_direct()
Date: Mon, 14 Apr 2025 16:05:28 +0900 [thread overview]
Message-ID: <20250414160528.3fd76062ad194bdffff515b5@kernel.org> (raw)
In-Reply-To: <20250413014444.36724-1-dongml2@chinatelecom.cn>
On Sun, 13 Apr 2025 09:44:44 +0800
Menglong Dong <menglong8.dong@gmail.com> wrote:
> The maximum of the ftrace hash bits is made fls(32) in
> register_ftrace_direct(), which seems illogical. So, we fix it by making
> the max hash bits FTRACE_HASH_MAX_BITS instead.
>
Loogs good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thanks!
> Fixes: d05cb470663a ("ftrace: Fix modification of direct_function hash while in use")
> Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> ---
> v2:
> - thanks for Steven's advice, we fix the problem by making the max hash
> bits FTRACE_HASH_MAX_BITS instead.
> ---
> kernel/trace/ftrace.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 1a48aedb5255..d153ad13e0e0 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -5914,9 +5914,10 @@ int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)
>
> /* Make a copy hash to place the new and the old entries in */
> size = hash->count + direct_functions->count;
> - if (size > 32)
> - size = 32;
> - new_hash = alloc_ftrace_hash(fls(size));
> + size = fls(size);
> + if (size > FTRACE_HASH_MAX_BITS)
> + size = FTRACE_HASH_MAX_BITS;
> + new_hash = alloc_ftrace_hash(size);
> if (!new_hash)
> goto out_unlock;
>
> --
> 2.39.5
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-04-14 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 1:44 [PATCH bpf v2] ftrace: fix incorrect hash size in register_ftrace_direct() Menglong Dong
2025-04-14 7:05 ` Masami Hiramatsu [this message]
2025-04-15 23:14 ` Andrii Nakryiko
2025-04-16 0:55 ` Steven Rostedt
2025-04-16 1:06 ` Menglong Dong
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=20250414160528.3fd76062ad194bdffff515b5@kernel.org \
--to=mhiramat@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dongml2@chinatelecom.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.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;
as well as URLs for NNTP newsgroup(s).