linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
	Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>,
	stable@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] tracing/kprobes: Fix symbol counting logic by looking at modules as well
Date: Sun, 29 Oct 2023 19:09:00 +0200	[thread overview]
Message-ID: <2711863.mvXUDI8C0e@pwmachine> (raw)
In-Reply-To: <20231027233126.2073148-1-andrii@kernel.org>

Hi!


Le samedi 28 octobre 2023, 02:31:26 EET Andrii Nakryiko a écrit :
> Recent changes to count number of matching symbols when creating
> a kprobe event failed to take into account kernel modules. As such, it
> breaks kprobes on kernel module symbols, by assuming there is no match.

Ah... Sorry about this...
Thank you for the fix, I will handle the patch for older kernels in case there 
are troubles applying it.
 
> Fix this my calling module_kallsyms_on_each_symbol() in addition to
> kallsyms_on_each_match_symbol() to perform a proper counting.
> 
> Cc: Francis Laniel <flaniel@linux.microsoft.com>
> Cc: stable@vger.kernel.org
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Fixes: b022f0c7e404 ("tracing/kprobes: Return EADDRNOTAVAIL when func
> matches several symbols") Signed-off-by: Andrii Nakryiko
> <andrii@kernel.org>
> ---
>  kernel/trace/trace_kprobe.c | 24 ++++++++++++++++++++----
>  1 file changed, 20 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index effcaede4759..1efb27f35963 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -714,14 +714,30 @@ static int count_symbols(void *data, unsigned long
> unused) return 0;
>  }
> 
> +struct sym_count_ctx {
> +	unsigned int count;
> +	const char *name;
> +};
> +
> +static int count_mod_symbols(void *data, const char *name, unsigned long
> unused) +{
> +	struct sym_count_ctx *ctx = data;
> +
> +	if (strcmp(name, ctx->name) == 0)
> +		ctx->count++;
> +
> +	return 0;
> +}
> +
>  static unsigned int number_of_same_symbols(char *func_name)
>  {
> -	unsigned int count;
> +	struct sym_count_ctx ctx = { .count = 0, .name = func_name };
> +
> +	kallsyms_on_each_match_symbol(count_symbols, func_name, &ctx.count);
> 
> -	count = 0;
> -	kallsyms_on_each_match_symbol(count_symbols, func_name, &count);
> +	module_kallsyms_on_each_symbol(NULL, count_mod_symbols, &ctx);
> 
> -	return count;
> +	return ctx.count;
>  }
> 
>  static int __trace_kprobe_create(int argc, const char *argv[])


Best regards.



      parent reply	other threads:[~2023-10-29 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 23:31 [PATCH] tracing/kprobes: Fix symbol counting logic by looking at modules as well Andrii Nakryiko
2023-10-27 23:37 ` Song Liu
2023-10-28  0:50   ` Masami Hiramatsu
2023-10-28  1:41 ` Masami Hiramatsu
2023-10-28  3:18   ` Masami Hiramatsu
2023-10-29 17:09 ` Francis Laniel [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=2711863.mvXUDI8C0e@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).