From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: Yujie Liu <yujie.liu@intel.com>,
<linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Tom Zanussi <zanussi@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/kprobes: Fix the order of argument descriptions
Date: Sat, 11 Nov 2023 08:01:57 +0900 [thread overview]
Message-ID: <20231111080157.1ad21fc9a236d69137d3a8c9@kernel.org> (raw)
In-Reply-To: <98413d47-986f-bf94-0793-865a5a4dc80d@quicinc.com>
On Tue, 31 Oct 2023 15:18:14 +0530
Mukesh Ojha <quic_mojha@quicinc.com> wrote:
>
>
> On 10/31/2023 9:43 AM, Yujie Liu wrote:
> > The order of descriptions should be consistent with the argument list of
> > the function, so "kretprobe" should be the second one.
> >
> > int __kprobe_event_gen_cmd_start(struct dynevent_cmd *cmd, bool kretprobe,
> > const char *name, const char *loc, ...)
> >
> > Fixes: 2a588dd1d5d6 ("tracing: Add kprobe event command generation functions")
> > Suggested-by: Mukesh Ojha <quic_mojha@quicinc.com>
> > Signed-off-by: Yujie Liu <yujie.liu@intel.com>
>
> Thanks.
>
> Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
OK, let me pick this to probes/fixes.
Thanks!
>
> -Mukesh
>
> > ---
> > kernel/trace/trace_kprobe.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> > index e834f149695b..47812aa16bb5 100644
> > --- a/kernel/trace/trace_kprobe.c
> > +++ b/kernel/trace/trace_kprobe.c
> > @@ -1020,9 +1020,9 @@ EXPORT_SYMBOL_GPL(kprobe_event_cmd_init);
> > /**
> > * __kprobe_event_gen_cmd_start - Generate a kprobe event command from arg list
> > * @cmd: A pointer to the dynevent_cmd struct representing the new event
> > + * @kretprobe: Is this a return probe?
> > * @name: The name of the kprobe event
> > * @loc: The location of the kprobe event
> > - * @kretprobe: Is this a return probe?
> > * @...: Variable number of arg (pairs), one pair for each field
> > *
> > * NOTE: Users normally won't want to call this function directly, but
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-11-10 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 4:13 Yujie Liu
2023-10-31 9:48 ` Mukesh Ojha
2023-11-10 23:01 ` 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=20231111080157.1ad21fc9a236d69137d3a8c9@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=yujie.liu@intel.com \
--cc=zanussi@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®