From: Cao Ruichuang <create0818@163.com>
To: mhiramat@kernel.org
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Account for fprobe attachment at creation
Date: Wed, 08 Apr 2026 12:09:16 +0800 [thread overview]
Message-ID: <177562135674.3342.17510076733132622922@163.com> (raw)
In-Reply-To: <20260408094920.417cbb5e64220afc2bf1b2aa@kernel.org>
Thanks, that is a good point.
I need to separate a clean source tree from a clean tracing runtime
environment. I will rerun this in a fresh tracing environment and
re-evaluate the testcase assumption before pushing anything further.
If this testcase is only valid for a clean environment, then an
unresolved check or a different precondition will make more sense
than the current patch.
Thanks,
Cao Ruichuang
next prev parent reply other threads:[~2026-04-08 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 11:57 [PATCH] selftests/ftrace: Account for fprobe attachment at creation Cao Ruichuang
2026-04-08 0:49 ` Masami Hiramatsu
2026-04-08 4:09 ` Cao Ruichuang [this message]
2026-04-09 5:18 ` Cao Ruichuang
2026-04-09 8:29 ` Masami Hiramatsu
2026-04-10 4:32 ` Cao Ruichuang
2026-04-13 8:48 ` Masami Hiramatsu
2026-04-08 4:25 ` [PATCH v2] selftests/ftrace: Account for fprobe attachment before enable 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=177562135674.3342.17510076733132622922@163.com \
--to=create0818@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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