From: David Laight <David.Laight@ACULAB.COM>
To: 'Steven Rostedt' <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tom Zanussi <zanussi@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v2 2/3] tracing: Add "(fault)" name injection to kernel probes
Date: Wed, 12 Oct 2022 12:34:45 +0000 [thread overview]
Message-ID: <13544aa157fc4083a59127bbc5a2bb1e@AcuMS.aculab.com> (raw)
In-Reply-To: <20221012104534.644803645@goodmis.org>
From: Steven Rostedt
> Sent: 12 October 2022 11:41
>
> Have the specific functions for kernel probes that read strings to inject
> the "(fault)" name directly. trace_probes.c does this too (for uprobes)
> but as the code to read strings are going to be used by synthetic events
> (and perhaps other utilities), it simplifies the code by making sure those
> other uses do not need to implement the "(fault)" name injection as well.
>
> Cc: stable@vger.kernel.org
> Fixes: bd82631d7ccdc ("tracing: Add support for dynamic strings to synthetic events")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_probe_kernel.h | 31 +++++++++++++++++++++++++------
> 1 file changed, 25 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/trace/trace_probe_kernel.h b/kernel/trace/trace_probe_kernel.h
> index 1d43df29a1f8..77dbd9ff9782 100644
> --- a/kernel/trace/trace_probe_kernel.h
> +++ b/kernel/trace/trace_probe_kernel.h
> @@ -2,6 +2,8 @@
> #ifndef __TRACE_PROBE_KERNEL_H_
> #define __TRACE_PROBE_KERNEL_H_
>
> +#define FAULT_STRING "(fault)"
> +
> /*
> * This depends on trace_probe.h, but can not include it due to
> * the way trace_probe_tmpl.h is used by trace_kprobe.c and trace_eprobe.c.
> @@ -13,8 +15,16 @@ static nokprobe_inline int
> kern_fetch_store_strlen_user(unsigned long addr)
> {
> const void __user *uaddr = (__force const void __user *)addr;
> + int ret;
>
> - return strnlen_user_nofault(uaddr, MAX_STRING_SIZE);
> + ret = strnlen_user_nofault(uaddr, MAX_STRING_SIZE);
> + /*
> + * strnlen_user_nofault returns zero on fault, insert the
> + * FAULT_STRING when that occurs.
> + */
> + if (ret <= 0)
> + return strlen(FAULT_STRING) + 1;
> + return ret;
> }
Isn't that going to do the wrong thing if the user
string is valid memory but just zero length??
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-10-12 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 10:40 [PATCH v2 0/3] tracing: Fix synthetic event bug Steven Rostedt
2022-10-12 10:40 ` [PATCH v2 1/3] tracing: Move duplicate code of trace_kprobe/eprobe.c into header Steven Rostedt
2022-10-12 10:40 ` [PATCH v2 2/3] tracing: Add "(fault)" name injection to kernel probes Steven Rostedt
2022-10-12 12:34 ` David Laight [this message]
2022-10-12 12:42 ` Steven Rostedt
2022-10-12 10:40 ` [PATCH v2 3/3] tracing: Fix reading strings from synthetic events Steven Rostedt
2022-10-12 12:46 ` [PATCH v2 0/3] tracing: Fix synthetic event bug Masami Hiramatsu
2022-10-12 15:06 ` Tom Zanussi
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=13544aa157fc4083a59127bbc5a2bb1e@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--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
Powered by JetHome