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:35:20 -0700 [thread overview]
Message-ID: <1c580335-a794-4307-a24f-39236064f8e8@oracle.com> (raw)
In-Reply-To: <20250327172050.2be5b38a@gandalf.local.home>
On 3/27/25 14:20, Steven Rostedt wrote:
> On Thu, 27 Mar 2025 14:00:44 -0700
> Libo Chen <libo.chen@oracle.com> wrote:
>
>>> 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.
>
> This shouldn't be a blocker for you. Do you get any errors?
>
> Hmm, if this causes bugs (perhaps you have arguments after the %*pbl) then
> I can add this as a fix and not an enhancement.
Not sure if I will call it an error. But without this patch, I will just get
"nil" when using %*p so this information is lost here. If I go ahead with
%*pbl, nodemask value will not show up in the trace until this one is merged.
Libo
>
> -- Steve
prev parent reply other threads:[~2025-03-27 21:35 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
2025-03-27 21:20 ` Steven Rostedt
2025-03-27 21:35 ` Libo Chen [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=1c580335-a794-4307-a24f-39236064f8e8@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