From: Masami Hiramatsu <mhiramat@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCH] tracing/kprobes: allow to create probe with a module name starting with a digit
Date: Tue, 27 Jun 2017 17:38:30 +0900 [thread overview]
Message-ID: <20170627173830.80e06e87716742a7cc4a6257@kernel.org> (raw)
In-Reply-To: <fd72d666f45b114e2c5b9cf7e27b91de1ec966f1.1498122881.git.sd@queasysnail.net>
On Thu, 22 Jun 2017 11:24:42 +0200
Sabrina Dubroca <sd@queasysnail.net> wrote:
> Always try to parse an address, since kstrtoul() will safely fail when
> given a symbol as input. If that fails (which will be the case for a
> symbol), try to parse a symbol instead.
>
> This allows creating a probe such as:
>
> p:probe/vlan_gro_receive 8021q:vlan_gro_receive+0
>
> Which is necessary for this command to work:
>
> perf probe -m 8021q -a vlan_gro_receive
>
Ah, I forgot that case.
Nice catch!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks!
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
> ---
> kernel/trace/trace_kprobe.c | 14 +++++---------
> 1 file changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index c129fca6ec99..b53c8d369163 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -707,20 +707,16 @@ static int create_trace_kprobe(int argc, char **argv)
> pr_info("Probe point is not specified.\n");
> return -EINVAL;
> }
> - if (isdigit(argv[1][0])) {
> - /* an address specified */
> - ret = kstrtoul(&argv[1][0], 0, (unsigned long *)&addr);
> - if (ret) {
> - pr_info("Failed to parse address.\n");
> - return ret;
> - }
> - } else {
> +
> + /* try to parse an address. if that fails, try to read the
> + * input as a symbol. */
> + if (kstrtoul(argv[1], 0, (unsigned long *)&addr)) {
> /* a symbol specified */
> symbol = argv[1];
> /* TODO: support .init module functions */
> ret = traceprobe_split_symbol_offset(symbol, &offset);
> if (ret) {
> - pr_info("Failed to parse symbol.\n");
> + pr_info("Failed to parse either an address or a symbol.\n");
> return ret;
> }
> if (offset && is_return &&
> --
> 2.13.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-06-27 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:24 Sabrina Dubroca
2017-06-27 8:38 ` Masami Hiramatsu [this message]
2017-06-27 14:07 ` Steven Rostedt
2017-06-27 22:05 ` Masami Hiramatsu
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=20170627173830.80e06e87716742a7cc4a6257@kernel.org \
--to=mhiramat@kernel.org \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sd@queasysnail.net \
/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®