From: Libo Chen <libo.chen@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing: Verify event formats that have "%*p.."
Date: Thu, 27 Mar 2025 14:00:44 -0700 [thread overview]
Message-ID: <d9707265-d6bd-40df-8e7f-4213851ea33f@oracle.com> (raw)
In-Reply-To: <20250327143853.1cef38af@gandalf.local.home>
On 3/27/25 11:38, Steven Rostedt wrote:
> On Thu, 27 Mar 2025 11:32:23 -0700
> Libo Chen <libo.chen@oracle.com> wrote:
>
>> On 3/27/25 08:49, Steven Rostedt wrote:
>>> From: Steven Rostedt <rostedt@goodmis.org>
>>>
>>> The trace event verifier checks the formats of trace events to make sure
>>> that they do not point at memory that is not in the trace event itself or
>>> in data that will never be freed. If an event references data that was
>>> allocated when the event triggered and that same data is freed before the
>>> event is read, then the kernel can crash by reading freed memory.
>>>
>>> The verifier runs at boot up (or module load) and scans the print formats
>>> of the events and checks their arguments to make sure that dereferenced
>>> pointers are safe. If the format uses "%*p.." the verifier will ignore it,
>>> and that could be dangerous. Cover this case as well.
>>>
>>> Also add to the sample code a use case of "%*pbl".
>>>
>>> Link: https://urldefense.com/v3/__https://lore.kernel.org/all/bcba4d76-2c3f-4d11-baf0-02905db953dd@oracle.com/__;!!ACWV5N9M2RV99hQ!LTIVO1_O9wY2hBAnpNF5zcB1EFlC77zOnu4oVcM4DoD77p5ZO_m1LFZdPVJPj4spzye4JntXHOqOVxirPQ$
>>>
>> Thanks Steve, a minor style issue below, otherwise LGTM. I have tested it, it works.
>>
>> Reviewed-by: Libo Chen <libo.chen@oracle.com>
>> Tested-by: Libo Chen <libo.chen@oracle.com>
>
> Thanks for testing.
>
>>> /*
>>> * Notice here the use of some helper functions. This includes:
>>> @@ -370,7 +371,10 @@ TRACE_EVENT(foo_bar,
>>>
>>> __get_str(str), __get_str(lstr),
>>> __get_bitmask(cpus), __get_cpumask(cpum),
>>> - __get_str(vstr))
>>> + __get_str(vstr),
>>> + __get_dynamic_array_len(cpus),
>>> + __get_dynamic_array_len(cpus),
>>> + __get_dynamic_array(cpus))
>>
>> __get_dynamic_array_len() calls don't seem to be aligned with the ones above
>>
>
> Ah yeah. I'll update. Note, this isn't going to go into the kernel until at
> least 6.16.
>
Okay thanks for the note. I will stick to %lx for now and change it to %*pbl
once this gets in.
Libo
> -- Steve
next prev parent reply other threads:[~2025-03-27 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 15:49 [PATCH] tracing: Verify event formats that have "%*p.." Steven Rostedt
2025-03-27 18:32 ` Libo Chen
2025-03-27 18:38 ` Steven Rostedt
2025-03-27 21:00 ` Libo Chen [this message]
2025-03-27 21:20 ` Steven Rostedt
2025-03-27 21:35 ` Libo Chen
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=d9707265-d6bd-40df-8e7f-4213851ea33f@oracle.com \
--to=libo.chen@oracle.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