public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Cao Ruichuang <create0818@163.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	shuah@kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Account for fprobe attachment at creation
Date: Mon, 13 Apr 2026 17:48:27 +0900	[thread overview]
Message-ID: <20260413174827.25a02a9dc83248eff3f6737c@kernel.org> (raw)
In-Reply-To: <20260410043243.65800-1-create0818@163.com>

On Fri, 10 Apr 2026 12:32:43 +0800
Cao Ruichuang <create0818@163.com> wrote:

> Hi Masami,
> 
> I reran this in clean QEMU on two kernels and got different results.
> 
> 1. Ubuntu distro kernel:
>    Linux 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC
>    Tue Jan 13 16:40:06 UTC 2026
> 
>    baseline count=2
>    after_create123 count=4
>    after_enable1/2/3 count=4
> 
>    baseline enabled_functions:
>      __hid_bpf_tail_call ...
> 
>    after_create123 enabled_functions:
>      kernel_clone (2) R ->arch_ftrace_ops_list_func+0x0/0x280
>      kmem_cache_free (1) R tramp: ... ->fprobe_handler+0x0/0x40
>      __hid_bpf_tail_call ...
> 
> 2. Current source-tree kernel built from the clean snapshot of my patch
>    branch:
>    Linux 7.0.0-rc6 #2 SMP PREEMPT_DYNAMIC Fri Apr 10 12:19:39 CST 2026
> 
>    baseline count=0
>    after_create123 count=0
>    after_enable1 count=1
>    after_enable2 count=1
>    after_enable3 count=2
> 
>    after_create123 enabled_functions:
>      <empty>
> 
>    after_enable3 enabled_functions:
>      kernel_clone (2) ->arch_ftrace_ops_list_func+0x0/0x200
>      kmem_cache_free (1) tramp: ... ->fprobe_ftrace_entry+0x0/0x220
> 
> So the behavior I reported earlier reproduces on that Ubuntu 6.8 kernel,
> but not on the current source-tree kernel. I think my earlier conclusion
> was too broad.

Thanks for reporting the difference of behaviors.

> 
> I will stop pushing this testcase change for now unless I can narrow down
> which kernel change caused the difference.

OK.

Thanks!

> 
> Thanks,
> Cao Ruichuang
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-04-13  8:48 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
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 [this message]
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=20260413174827.25a02a9dc83248eff3f6737c@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=create0818@163.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=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