From: Leo Yan <leo.yan@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.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] tracing: Consider the NULL character when validating the event length
Date: Mon, 7 Oct 2024 15:33:47 +0100 [thread overview]
Message-ID: <fdad61fc-c3cf-43b4-a049-b428ea89013f@arm.com> (raw)
In-Reply-To: <20241007102242.18d2636e@gandalf.local.home>
On 10/7/24 15:22, Steven Rostedt wrote:
> Warning: EXTERNAL SENDER, use caution when opening links or attachments.
>
>
> On Mon, 7 Oct 2024 14:51:26 +0100
> Leo Yan <leo.yan@arm.com> wrote:
>
>> strlen() returns a string length excluding the null byte. This commit
>> adds 1 to account for the NULL terminating character when checking if an
>> event string is within the maximum length.
>>
>> Fixes: dec65d79fd26 ("tracing/probe: Check event name length correctly")
>> Signed-off-by: Leo Yan <leo.yan@arm.com>
>> ---
>> 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..376ba56c3680 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 + 1 > MAX_EVENT_NAME_LEN) {
>
> Usually, the check is:
>
> } else if (len >= MAX_EVENT_NAME_LEN) {
>
> Which is a better way to check max length.
Will update. Thanks for suggestion.
Leo
prev parent reply other threads:[~2024-10-07 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:51 Leo Yan
2024-10-07 14:22 ` Steven Rostedt
2024-10-07 14:33 ` Leo Yan [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=fdad61fc-c3cf-43b4-a049-b428ea89013f@arm.com \
--to=leo.yan@arm.com \
--cc=Dave.Martin@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--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
all inboxes | Powered by JetHome®