From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Shuah Khan <shuah@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Add required dependency for kprobe tests
Date: Thu, 15 Aug 2024 00:45:09 +0900 [thread overview]
Message-ID: <20240815004509.b5252f43379124b4ea9c26f5@kernel.org> (raw)
In-Reply-To: <9016df04-041b-4837-9590-1c5159609826@linuxfoundation.org>
On Wed, 14 Aug 2024 05:43:29 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 8/13/24 18:53, Masami Hiramatsu (Google) wrote:
> > Hi Shuah,
> >
> > Can you pick this? I confirmed this can be applied on v6.11-rc3.
> >
> >
> >
> > On Thu, 13 Jun 2024 07:12:10 +0900
> > "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> >
> >> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >>
> >> kprobe_args_{char,string}.tc are using available_filter_functions file
> >> which is provided by function tracer. Thus if function tracer is disabled,
> >> these tests are failed on recent kernels because tracefs_create_dir is
> >> not raised events by adding a dynamic event.
> >> Add available_filter_functions to requires line.
> >>
> >> Fixes: 7c1130ea5cae ("test: ftrace: Fix kprobe test for eventfs")
> >> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Applied to linux-kselftest next for Linux 6.12-rc1
Thanks!
>
> thanks,
> -- Shuah
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-08-14 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 22:12 [PATCH] selftests/ftrace: Add required dependency for kprobe tests Masami Hiramatsu (Google)
2024-08-14 0:53 ` Masami Hiramatsu
2024-08-14 11:43 ` Shuah Khan
2024-08-14 15:45 ` Masami Hiramatsu [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=20240815004509.b5252f43379124b4ea9c26f5@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.