From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Xuefeng Li <lixuefeng@loongson.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] samples: Use KSYM_NAME_LEN for kprobes
Date: Wed, 22 Jun 2022 11:06:59 +0900 [thread overview]
Message-ID: <20220622110659.74a269678bc7c37e15cdebaf@kernel.org> (raw)
In-Reply-To: <1654651402-21552-1-git-send-email-yangtiezhu@loongson.cn>
Hi,
On Wed, 8 Jun 2022 09:23:22 +0800
Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
> It is better and enough to use KSYM_NAME_LEN for kprobes
> in samples, no need to define and use the other values.
This looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you!
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> samples/kprobes/kprobe_example.c | 5 ++---
> samples/kprobes/kretprobe_example.c | 5 ++---
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/samples/kprobes/kprobe_example.c b/samples/kprobes/kprobe_example.c
> index f991a66..fd346f5 100644
> --- a/samples/kprobes/kprobe_example.c
> +++ b/samples/kprobes/kprobe_example.c
> @@ -16,9 +16,8 @@
> #include <linux/module.h>
> #include <linux/kprobes.h>
>
> -#define MAX_SYMBOL_LEN 64
> -static char symbol[MAX_SYMBOL_LEN] = "kernel_clone";
> -module_param_string(symbol, symbol, sizeof(symbol), 0644);
> +static char symbol[KSYM_NAME_LEN] = "kernel_clone";
> +module_param_string(symbol, symbol, KSYM_NAME_LEN, 0644);
>
> /* For each probe you need to allocate a kprobe structure */
> static struct kprobe kp = {
> diff --git a/samples/kprobes/kretprobe_example.c b/samples/kprobes/kretprobe_example.c
> index 228321e..cbf1654 100644
> --- a/samples/kprobes/kretprobe_example.c
> +++ b/samples/kprobes/kretprobe_example.c
> @@ -23,11 +23,10 @@
> #include <linux/module.h>
> #include <linux/kprobes.h>
> #include <linux/ktime.h>
> -#include <linux/limits.h>
> #include <linux/sched.h>
>
> -static char func_name[NAME_MAX] = "kernel_clone";
> -module_param_string(func, func_name, NAME_MAX, S_IRUGO);
> +static char func_name[KSYM_NAME_LEN] = "kernel_clone";
> +module_param_string(func, func_name, KSYM_NAME_LEN, 0644);
> MODULE_PARM_DESC(func, "Function to kretprobe; this module will report the"
> " function's execution time");
>
> --
> 2.1.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2022-06-22 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 1:23 [PATCH v2] samples: Use KSYM_NAME_LEN for kprobes Tiezhu Yang
2022-06-21 11:44 ` Tiezhu Yang
2022-06-22 2:06 ` Masami Hiramatsu [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=20220622110659.74a269678bc7c37e15cdebaf@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=rostedt@goodmis.org \
--cc=yangtiezhu@loongson.cn \
/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