From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Florent Revest <revest@chromium.org>
Cc: linux-trace-kernel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
bpf <bpf@vger.kernel.org>, Sven Schnelle <svens@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alan Maguire <alan.maguire@oracle.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Guo Ren <guoren@kernel.org>
Subject: [PATCH v4 32/33] selftests: ftrace: Remove obsolate maxactive syntax check
Date: Fri, 8 Dec 2023 19:30:44 +0900 [thread overview]
Message-ID: <170203144437.579004.4423247283109714307.stgit@devnote2> (raw)
In-Reply-To: <170203105427.579004.8033550792660734570.stgit@devnote2>
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Since the fprobe event does not support maxactive anymore, stop
testing the maxactive syntax error checking.
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
---
.../ftrace/test.d/dynevent/fprobe_syntax_errors.tc | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc b/tools/testing/selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc
index 20e42c030095..66516073ff27 100644
--- a/tools/testing/selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc
+++ b/tools/testing/selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc
@@ -16,9 +16,7 @@ aarch64)
REG=%r0 ;;
esac
-check_error 'f^100 vfs_read' # MAXACT_NO_KPROBE
-check_error 'f^1a111 vfs_read' # BAD_MAXACT
-check_error 'f^100000 vfs_read' # MAXACT_TOO_BIG
+check_error 'f^100 vfs_read' # BAD_MAXACT
check_error 'f ^non_exist_func' # BAD_PROBE_ADDR (enoent)
check_error 'f ^vfs_read+10' # BAD_PROBE_ADDR
next prev parent reply other threads:[~2023-12-08 10:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:24 [PATCH v4 00/33] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph Masami Hiramatsu (Google)
2023-12-08 10:24 ` [PATCH v4 01/33] tracing: Add a comment about ftrace_regs definition Masami Hiramatsu (Google)
2023-12-08 10:24 ` [PATCH v4 02/33] x86: tracing: Add ftrace_regs definition in the header Masami Hiramatsu (Google)
2023-12-08 10:24 ` [PATCH v4 03/33] function_graph: Convert ret_stack to a series of longs Masami Hiramatsu (Google)
2023-12-08 10:25 ` [PATCH v4 04/33] fgraph: Use BUILD_BUG_ON() to make sure we have structures divisible by long Masami Hiramatsu (Google)
2023-12-08 10:25 ` [PATCH v4 05/33] function_graph: Add an array structure that will allow multiple callbacks Masami Hiramatsu (Google)
2023-12-08 10:25 ` [PATCH v4 06/33] function_graph: Allow multiple users to attach to function graph Masami Hiramatsu (Google)
2023-12-08 10:25 ` [PATCH v4 07/33] function_graph: Remove logic around ftrace_graph_entry and return Masami Hiramatsu (Google)
2023-12-08 10:25 ` [PATCH v4 08/33] ftrace/function_graph: Pass fgraph_ops to function graph callbacks Masami Hiramatsu (Google)
2023-12-08 10:26 ` [PATCH v4 09/33] ftrace: Allow function_graph tracer to be enabled in instances Masami Hiramatsu (Google)
2023-12-08 10:26 ` [PATCH v4 10/33] ftrace: Allow ftrace startup flags exist without dynamic ftrace Masami Hiramatsu (Google)
2023-12-08 10:26 ` [PATCH v4 11/33] function_graph: Have the instances use their own ftrace_ops for filtering Masami Hiramatsu (Google)
2023-12-08 10:26 ` [PATCH v4 12/33] function_graph: Use a simple LRU for fgraph_array index number Masami Hiramatsu (Google)
2023-12-08 10:26 ` [PATCH v4 13/33] function_graph: Add "task variables" per task for fgraph_ops Masami Hiramatsu (Google)
2023-12-08 10:27 ` [PATCH v4 14/33] function_graph: Move set_graph_function tests to shadow stack global var Masami Hiramatsu (Google)
2023-12-08 10:27 ` [PATCH v4 15/33] function_graph: Move graph depth stored data " Masami Hiramatsu (Google)
2023-12-08 10:27 ` [PATCH v4 16/33] function_graph: Move graph notrace bit " Masami Hiramatsu (Google)
2023-12-08 10:27 ` [PATCH v4 17/33] function_graph: Implement fgraph_reserve_data() and fgraph_retrieve_data() Masami Hiramatsu (Google)
2023-12-08 10:27 ` [PATCH v4 18/33] function_graph: Add selftest for passing local variables Masami Hiramatsu (Google)
2023-12-08 10:28 ` [PATCH v4 19/33] function_graph: Add a new entry handler with parent_ip and ftrace_regs Masami Hiramatsu (Google)
2023-12-08 10:28 ` [PATCH v4 20/33] function_graph: Add a new exit " Masami Hiramatsu (Google)
2023-12-08 10:28 ` [PATCH v4 21/33] x86/ftrace: Enable HAVE_FUNCTION_GRAPH_FREGS Masami Hiramatsu (Google)
2023-12-08 10:28 ` [PATCH v4 22/33] tracing: Rename ftrace_regs_return_value to ftrace_regs_get_return_value Masami Hiramatsu (Google)
2023-12-08 10:28 ` [PATCH v4 23/33] arm64: ftrace: Enable HAVE_FUNCTION_GRAPH_FREGS Masami Hiramatsu (Google)
2023-12-08 10:29 ` [PATCH v4 24/33] fprobe: Use ftrace_regs in fprobe entry handler Masami Hiramatsu (Google)
2023-12-08 10:29 ` [PATCH v4 25/33] fprobe: Use ftrace_regs in fprobe exit handler Masami Hiramatsu (Google)
2023-12-08 10:29 ` [PATCH v4 26/33] tracing: Add ftrace_partial_regs() for converting ftrace_regs to pt_regs Masami Hiramatsu (Google)
2023-12-08 10:29 ` [PATCH v4 27/33] tracing: Add ftrace_fill_perf_regs() for perf event Masami Hiramatsu (Google)
2023-12-08 10:29 ` [PATCH v4 28/33] fprobe: Rewrite fprobe on function-graph tracer Masami Hiramatsu (Google)
2023-12-08 10:30 ` [PATCH v4 29/33] tracing/fprobe: Remove nr_maxactive from fprobe Masami Hiramatsu (Google)
2023-12-08 10:30 ` [PATCH v4 30/33] tracing/fprobe: Enable fprobe events with CONFIG_DYNAMIC_FTRACE_WITH_ARGS Masami Hiramatsu (Google)
2023-12-08 10:30 ` [PATCH v4 31/33] bpf: Enable kprobe_multi feature if CONFIG_FPROBE is enabled Masami Hiramatsu (Google)
2023-12-08 10:30 ` Masami Hiramatsu (Google) [this message]
2023-12-08 10:30 ` [PATCH v4 33/33] Documentation: probes: Update fprobe on function-graph tracer 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=170203144437.579004.4423247283109714307.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=guoren@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=peterz@infradead.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
/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).