linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Shuah Khan <shuah@kernel.org>, Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: [PATCH 0/3] selftests/tracing: Fix some testcases for recent change
Date: Sat,  7 Jan 2023 22:32:08 +0900	[thread overview]
Message-ID: <167309832823.640500.13244630381161014364.stgit@devnote3> (raw)

This includes some patches to fix 2 issues on ftrace selftests.

- eprobe filter and eprobe syntax test case were introduced but it
  doesn't check whether the kernel supports eprobe filter. Thus the
  new test case fails on the kernel which has eprobe but not support
  eprobe filter. To solve this issue, add a filter description to
  README file [1/3] and run the filter syntax error test only if the
  description is found in the README file [2/3].

- Recently objtool adds prefix symbols for the function padding nops,
  and the probepoint test case fails because this probepoint test case
  tests whether the kprobe event can probe the target function and the
  functions next to the target function. But the prefix symbols can not
  be probed. Thus these prefix symbols must be skipped [3/3].

Thank you,

---

Masami Hiramatsu (Google) (3):
      tracing/eprobe: Fix to add filter on eprobe description in README file
      selftests/ftrace: Fix eprobe syntax test case to check filter support
      selftests/ftrace: Fix probepoint testcase to ignore __pfx_* symbols


 kernel/trace/trace.c                               |    2 +-
 .../test.d/dynevent/eprobes_syntax_errors.tc       |    4 +++-
 .../selftests/ftrace/test.d/kprobe/probepoint.tc   |    2 +-
 3 files changed, 5 insertions(+), 3 deletions(-)

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

             reply	other threads:[~2023-01-07 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 13:32 Masami Hiramatsu (Google) [this message]
2023-01-07 13:32 ` [PATCH 1/3] tracing/eprobe: Fix to add filter on eprobe description in README file Masami Hiramatsu (Google)
2023-01-07 13:32 ` [PATCH 2/3] selftests/ftrace: Fix eprobe syntax test case to check filter support Masami Hiramatsu (Google)
2023-01-07 13:32 ` [PATCH 3/3] selftests/ftrace: Fix probepoint testcase to ignore __pfx_* symbols Masami Hiramatsu (Google)
2023-01-08 21:31 ` [PATCH 0/3] selftests/tracing: Fix some testcases for recent change Steven Rostedt
2023-01-26 20:43   ` Shuah Khan
  -- strict thread matches above, loose matches on Subject: below --
2023-01-07 13:31 Masami Hiramatsu (Google)

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=167309832823.640500.13244630381161014364.stgit@devnote3 \
    --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 \
    /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;
as well as URLs for NNTP newsgroup(s).