From: Steven Rostedt <rostedt@goodmis.org>
To: CaoRuichuang <create0818@163.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: report header_page overwrite as signed char
Date: Mon, 6 Apr 2026 12:45:23 -0400 [thread overview]
Message-ID: <20260406124523.514ac754@gandalf.local.home> (raw)
In-Reply-To: <20260406162843.41592-1-create0818@163.com>
On Tue, 7 Apr 2026 00:28:43 +0800
CaoRuichuang <create0818@163.com> wrote:
> The header_page tracefs metadata currently reports overwrite as an
> int field with size 1. That makes parsers warn about a type and
> size mismatch even though the field is only used as a one-byte flag
> within commit.
>
> Keep the shared offset with commit as-is, but report overwrite as
> signed char so the declared type matches the hardcoded size and the
> emitted signedness.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=216999
> Signed-off-by: CaoRuichuang <create0818@163.com>
> ---
> kernel/trace/ring_buffer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 170170bd8..c4c2361b0 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -627,11 +627,11 @@ int ring_buffer_print_page_header(struct trace_buffer *buffer, struct trace_seq
> (unsigned int)sizeof(field.commit),
> (unsigned int)is_signed_type(long));
>
> - trace_seq_printf(s, "\tfield: int overwrite;\t"
> + trace_seq_printf(s, "\tfield: signed char overwrite;\t"
From the Bugzilla, the issue was with the rust parser. Would this still not
cause a warning if the "int" was switched to "char" and not "signed char".
The signed is redundant as it is already specified in the fields.
-- Steve
> "offset:%u;\tsize:%u;\tsigned:%u;\n",
> (unsigned int)offsetof(typeof(field), commit),
> 1,
> - (unsigned int)is_signed_type(long));
> + (unsigned int)is_signed_type(signed char));
>
> trace_seq_printf(s, "\tfield: char data;\t"
> "offset:%u;\tsize:%u;\tsigned:%u;\n",
next prev parent reply other threads:[~2026-04-06 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 16:28 [PATCH] ring-buffer: report header_page overwrite as signed char CaoRuichuang
2026-04-06 16:45 ` Steven Rostedt [this message]
2026-04-06 16:53 ` [PATCH v2] ring-buffer: report header_page overwrite as char Cao Ruichuang
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=20260406124523.514ac754@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=create0818@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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