Linux Trace Kernel
 help / color / mirror / Atom feed
From: Tianchen Ding <dtcccc@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftests/ftrace: Fix trace_marker_raw test on 64K page kernels
Date: Fri, 29 May 2026 10:59:34 +0800	[thread overview]
Message-ID: <bcb52d91-0440-4e73-86af-997e8b723711@linux.alibaba.com> (raw)
In-Reply-To: <20260528091348.71ae3aa3@fedora>



On 5/28/26 9:13 PM, Steven Rostedt wrote:
> On Thu, 28 May 2026 10:24:17 +0800
> Tianchen Ding <dtcccc@linux.alibaba.com> wrote:
> 
>>
>> diff --git a/tools/testing/selftests/ftrace/test.d/00basic/trace_marker_raw.tc b/tools/testing/selftests/ftrace/test.d/00basic/trace_marker_raw.tc
>> index 8e905d4fe6dd..f68f1901f65f 100644
>> --- a/tools/testing/selftests/ftrace/test.d/00basic/trace_marker_raw.tc
>> +++ b/tools/testing/selftests/ftrace/test.d/00basic/trace_marker_raw.tc
>> @@ -43,8 +43,11 @@ write_buffer() {
>>   	id=$1
>>   	size=$2
>>   
>> -	# write the string into the raw marker
>> -	make_str $id $size > trace_marker_raw
>> +	# Pipe through dd to ensure a single atomic write() syscall
>> +	# on architectures with 64K pages, where shell's printf builtin
>> +	# uses stdio buffering which may split the output into multiple
>> +	# writes.
>> +	make_str $id $size | dd of=trace_marker_raw bs=`expr $size + 4` iflag=fullblock
> 
> I was looking at this more, and I'm not comfortable with the hard coded
> 4 above. I rather use the length of the string. Something like:
> 
> 	str=`make_str $id $size`
> 	len=${#str}
> 	echo "$str" | dd of=trace_marker_raw bs=$len iflag=fullblock
> 
> -- Steve
> 

Capturing make_str output into a shell variable doesn't work because make_str 
outputs raw binary that may contain NUL bytes, and shell command substitution 
silently strips them.

However, the val variable inside make_str doesn't hold actual NUL bytes — it 
holds the text of escape sequences (e.g., the literal characters 
\003\000\000\000). The binary conversion only happens at the final printf 
"${val}${data}".

We can take advantage of this by having make_str return the escape-sequence text 
instead of binary, and letting write_buffer handle the conversion:

   make_str() {
         ...
         printf '%s' "${val}${data}"
   }

   write_buffer() {
         id=$1
         size=$2

         str=`make_str $id $size`
         len=$(printf "$str" | wc -c)
         printf "$str" | dd of=trace_marker_raw bs=$len iflag=fullblock
   }

This way str holds only printable escape-sequence text (no NUL), printf "$str" 
converts it to real binary through the pipe, and wc -c measures the true binary 
length.

>>   }
>>   
>>   


  reply	other threads:[~2026-05-29  2:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27  9:54 [PATCH] selftests/ftrace: Fix trace_marker_raw test on 64K page kernels Tianchen Ding
2026-05-27 14:09 ` Steven Rostedt
2026-05-28  2:24 ` [PATCH v2] " Tianchen Ding
2026-05-28 13:13   ` Steven Rostedt
2026-05-29  2:59     ` Tianchen Ding [this message]
2026-05-29 13:15       ` Steven Rostedt
2026-06-01  2:32 ` [PATCH v3] " Tianchen Ding

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=bcb52d91-0440-4e73-86af-997e8b723711@linux.alibaba.com \
    --to=dtcccc@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@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