Linux Trace Kernel
 help / color / mirror / Atom feed
From: Cao Ruichuang <create0818@163.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Daniel Gomez <da.gomez@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Aaron Tomlin <atomlin@atomlin.com>, Shuah Khan <shuah@kernel.org>,
	linux-trace-kernel@vger.kernel.org,
	linux-modules@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tracing: Export live module tracepoint strings in printk_formats
Date: Tue, 08 Sep 2026 05:18:23 +0000	[thread overview]
Message-ID: <5ba26e8ce9dd4d51ab4ff7c75f14b139@163.com> (raw)
In-Reply-To: <178647423521.280401.10184675433127100074@163.com>

Hi Steven,

Gentle ping on this v3.

While rechecking the selftest, I found that the unload checks can miss a
failure: if the first test string remains in printk_formats but the
second is gone, the test still passes. The first negated grep returns
nonzero, but set -e does not terminate the script for a negated command.
I reproduced this with a fixture containing only the first string.

I would add explicit failure handling (|| exit_fail) to both checks.
Would you prefer a v4 with this correction?

I can also make the final rmmod failure fatal and add a comment explaining
that trace_bprintk_fmt_cnt counts permanently retained, unique formats
and therefore is not decremented on module unload.

The current test checks the exported mappings, but does not exercise the
new membership lookup through a TRACE_EVENT and the tp_printk path. I can
extend coverage there as well if you would like it included in v4.

Thanks,
Cao Ruichuang


      reply	other threads:[~2026-09-08  5:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 17:09 [PATCH] tracing: preserve module tracepoint strings Cao Ruichuang
2026-04-08 20:32 ` Steven Rostedt
2026-04-09 12:37 ` Petr Pavlu
2026-04-10  5:18 ` [PATCH v2] " Cao Ruichuang
2026-04-13  9:40   ` Petr Pavlu
2026-04-13 12:33     ` [PATCH] tracing: separate module tracepoint strings from trace_printk formats Cao Ruichuang
2026-04-14 11:37       ` Petr Pavlu
2026-04-16  8:03         ` Cao Ruichuang
2026-04-20  6:19       ` [PATCH v2] tracing: export live module tracepoint strings in printk_formats Cao Ruichuang
2026-04-28 12:39         ` Steven Rostedt
2026-08-11 18:15           ` [PATCH v3] tracing: Export " Cao Ruichuang
2026-09-08  5:18             ` Cao Ruichuang [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=5ba26e8ce9dd4d51ab4ff7c75f14b139@163.com \
    --to=create0818@163.com \
    --cc=atomlin@atomlin.com \
    --cc=da.gomez@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=samitolvanen@google.com \
    --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