From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Dave.Martin@arm.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Consider the NULL character when validating the event length
Date: Fri, 11 Oct 2024 00:15:24 +0900 [thread overview]
Message-ID: <20241011001524.773836a84af82edede5349b2@kernel.org> (raw)
In-Reply-To: <20241007144724.920954-1-leo.yan@arm.com>
On Mon, 7 Oct 2024 15:47:24 +0100
Leo Yan <leo.yan@arm.com> wrote:
> strlen() returns a string length excluding the null byte. If the string
> length equals to the maximum buffer length, the buffer will have no
> space for the NULL terminating character.
>
> This commit checks this condition and returns failure for it.
>
Ah, good catch! The traceprobe_parse_event_name() requires
MAX_EVENT_NAME_LEN buffer.
----
/* @buf must has MAX_EVENT_NAME_LEN size */
int traceprobe_parse_event_name(const char **pevent, const char **pgroup,
----
But the macro name is a bit confusing. We may need below and use it around.
#define EVENT_NAME_BUFSIZE (MAX_EVENT_NAME_LEN + 1)
Anyway, I think this fix is correct.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you,
> Fixes: dec65d79fd26 ("tracing/probe: Check event name length correctly")
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
>
> Changes from v1:
> Refined for condition checking (Steve).
>
> kernel/trace/trace_probe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> index 39877c80d6cb..16a5e368e7b7 100644
> --- a/kernel/trace/trace_probe.c
> +++ b/kernel/trace/trace_probe.c
> @@ -276,7 +276,7 @@ int traceprobe_parse_event_name(const char **pevent, const char **pgroup,
> }
> trace_probe_log_err(offset, NO_EVENT_NAME);
> return -EINVAL;
> - } else if (len > MAX_EVENT_NAME_LEN) {
> + } else if (len >= MAX_EVENT_NAME_LEN) {
> trace_probe_log_err(offset, EVENT_TOO_LONG);
> return -EINVAL;
> }
> --
> 2.34.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-10-10 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:47 [PATCH v2] tracing: Consider the NULL character when validating the event length Leo Yan
2024-10-07 15:43 ` Steven Rostedt
2024-10-10 15:15 ` 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=20241011001524.773836a84af82edede5349b2@kernel.org \
--to=mhiramat@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.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).