From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Oleg Nesterov <oleg@redhat.com>, Jianlin Lv <Jianlin.Lv@arm.com>,
mingo@redhat.com, mhiramat@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tracing: precise log info for kretprobe addr err
Date: Tue, 26 Jan 2021 13:15:36 +0900 [thread overview]
Message-ID: <20210126131536.f6e3a737a7b948799084fa7a@kernel.org> (raw)
In-Reply-To: <20210125133840.511b1496@gandalf.local.home>
On Mon, 25 Jan 2021 13:38:40 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 25 Jan 2021 19:19:27 +0100
> Oleg Nesterov <oleg@redhat.com> wrote:
>
> > On 01/26, Jianlin Lv wrote:
> > >
> > > When trying to create kretprobe with the wrong function symbol in tracefs;
> > > The error is triggered in the register_trace_kprobe() and recorded as
> > > FAIL_REG_PROBE issue,
> > >
> > > Example:
> > > $ cd /sys/kernel/debug/tracing
> > > $ echo 'r:myprobe ERROR_SYMBOL_XXX ret=%x0' >> kprobe_events
> > > bash: echo: write error: Invalid argument
> > > $ cat error_log
> > > [142797.347877] trace_kprobe: error: Failed to register probe event
> > > Command: r:myprobe ERROR_SYMBOL_XXX ret=%x0
> > > ^
> > >
> > > This error can be detected in the parameter parsing stage, the effect of
> > > applying this patch is as follows:
> > >
> > > $ echo 'r:myprobe ERROR_SYMBOL_XXX ret=%x0' >> kprobe_events
> > > bash: echo: write error: Invalid argument
> > > $ cat error_log
> > > [415.89]trace_kprobe: error: Retprobe address must be an function entry
> > > Command: r:myprobe ERROR_SYMBOL_XXX ret=%x0
> >
> > IOW, the "offset != 0" check removed by this patch is obviously wrong, right?
> >
No, not wrong. Even offset != 0, if the symbol exists in the kernel,
kprobe_on_func_entry() will check it.
> > Agreed, but...
> >
> > > --- a/kernel/trace/trace_kprobe.c
> > > +++ b/kernel/trace/trace_kprobe.c
> > > @@ -830,7 +830,7 @@ static int trace_kprobe_create(int argc, const char *argv[])
> > > flags |= TPARG_FL_RETURN;
> > > if (kprobe_on_func_entry(NULL, symbol, offset))
> > > flags |= TPARG_FL_FENTRY;
> > > - if (offset && is_return && !(flags & TPARG_FL_FENTRY)) {
> > > + if (!strchr(symbol, ':') && is_return && !(flags & TPARG_FL_FENTRY)) {
> >
> > but why did you add the strchr(':') check instead?
> >
> > I was really puzzled until I found the this email from Masami:
> > https://lore.kernel.org/lkml/20210120131406.5a992c1e434681750a0cd5d4@kernel.org/
> >
> > So I leave this to you and Masami, but perhaps you can document this check at
> > least in the changelog?
> >
>
> No, you are correct. That needs to be documented in the code.
Agreed. There should be commented that is defered until the module is loaded.
>
> I was about to comment that the check requires a comment ;-)
>
> Jianlin,
>
> Care to send a v4 of the patch with a comment to why we are checking the
> symbol for ':'.
Thank you!
>
> Thanks!
>
> -- Steve
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-01-26 11:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 16:01 [PATCH v3] tracing: precise log info for kretprobe addr err Jianlin Lv
2021-01-25 18:19 ` Oleg Nesterov
2021-01-25 18:38 ` Steven Rostedt
2021-01-26 4:15 ` Masami Hiramatsu [this message]
2021-01-26 10:02 ` Jianlin Lv
2021-01-26 20:20 ` Oleg Nesterov
2021-01-26 20:43 ` Steven Rostedt
2021-01-26 21:17 ` Oleg Nesterov
2021-01-26 21:40 ` Steven Rostedt
2021-01-27 2:14 ` Masami Hiramatsu
2021-01-27 2:02 ` Masami Hiramatsu
2021-01-27 2:46 ` Jianlin Lv
2021-01-27 13:27 ` Masami Hiramatsu
2021-01-27 14:25 ` Jianlin Lv
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=20210126131536.f6e3a737a7b948799084fa7a@kernel.org \
--to=mhiramat@kernel.org \
--cc=Jianlin.Lv@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.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).