mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: alexei.starovoitov@gmail.com, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, hca@linux.ibm.com,
	revest@chromium.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH RFC bpf-next v2 1/4] fprobe: use rhltable for fprobe_ip_table
Date: Tue, 29 Jul 2025 10:42:54 +0900	[thread overview]
Message-ID: <20250729104254.560beac056de20d6aebe1d55@kernel.org> (raw)
In-Reply-To: <20250728072637.1035818-2-dongml2@chinatelecom.cn>

Hi,

I'll check it deeper, but 2 nits I found.

On Mon, 28 Jul 2025 15:22:50 +0800
Menglong Dong <menglong8.dong@gmail.com> wrote:

> diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
> index ba7ff14f5339..640a0c47fc76 100644
> --- a/kernel/trace/fprobe.c
> +++ b/kernel/trace/fprobe.c
> @@ -12,6 +12,7 @@
>  #include <linux/mutex.h>
>  #include <linux/slab.h>
>  #include <linux/sort.h>
> +#include <linux/rhashtable.h>

nit: Can you sort this alphabetically?

[...]
> @@ -249,9 +251,10 @@ static inline int __fprobe_kprobe_handler(unsigned long ip, unsigned long parent
>  static int fprobe_entry(struct ftrace_graph_ent *trace, struct fgraph_ops *gops,
>  			struct ftrace_regs *fregs)
>  {
> -	struct fprobe_hlist_node *node, *first;
> +	struct fprobe_hlist_node *node;
>  	unsigned long *fgraph_data = NULL;
>  	unsigned long func = trace->func;
> +	struct rhlist_head *head, *pos;

nit: Can you sort this as reverse Christmas tree? (like as below)

>  	unsigned long *fgraph_data = NULL;
>  	unsigned long func = trace->func;
> +	struct fprobe_hlist_node *node;
> +	struct rhlist_head *head, *pos;


>  	unsigned long ret_ip;
>  	int reserved_words;
>  	struct fprobe *fp;

Thank you,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2025-07-29  1:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  7:22 [PATCH RFC bpf-next v2 0/4] fprobe: use rhashtable " Menglong Dong
2025-07-28  7:22 ` [PATCH RFC bpf-next v2 1/4] fprobe: use rhltable " Menglong Dong
2025-07-29  1:42   ` Masami Hiramatsu [this message]
2025-07-29  1:55     ` Menglong Dong
2025-07-28  7:22 ` [PATCH RFC bpf-next v2 2/4] selftests/bpf: move get_ksyms and get_addrs to trace_helpers.c Menglong Dong
2025-07-28  7:22 ` [PATCH RFC bpf-next v2 3/4] selftests/bpf: skip recursive functions for kprobe_multi Menglong Dong
2025-07-28  7:22 ` [PATCH RFC bpf-next v2 4/4] selftests/bpf: add benchmark testing for kprobe-multi-all Menglong Dong
2025-07-28 12:35 ` [PATCH RFC bpf-next v2 0/4] fprobe: use rhashtable for fprobe_ip_table Masami Hiramatsu
2025-07-28 14:26   ` Menglong Dong
2025-07-28 23:53     ` Masami Hiramatsu
2025-07-28 13:59 ` Jiri Olsa
2025-07-28 14:27   ` Menglong Dong
2025-07-28 14:52   ` 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=20250729104254.560beac056de20d6aebe1d55@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=menglong8.dong@gmail.com \
    --cc=revest@chromium.org \
    --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®