From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Beau Belgrave <beaub@linux.microsoft.com>
Subject: [for-linus][PATCH 2/9] selftests/user_events: Add non-spacing separator check
Date: Fri, 03 May 2024 18:50:15 -0400 [thread overview]
Message-ID: <20240503225033.758019899@goodmis.org> (raw)
In-Reply-To: 20240503225013.519028385@goodmis.org
From: Beau Belgrave <beaub@linux.microsoft.com>
The ABI documentation indicates that field separators do not need a
space between them, only a ';'. When no spacing is used, the register
must work. Any subsequent register, with or without spaces, must match
and not return -EADDRINUSE.
Add a non-spacing separator case to our self-test register case to ensure
it works going forward.
Link: https://lore.kernel.org/linux-trace-kernel/20240423162338.292-3-beaub@linux.microsoft.com
Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
tools/testing/selftests/user_events/ftrace_test.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/testing/selftests/user_events/ftrace_test.c b/tools/testing/selftests/user_events/ftrace_test.c
index dcd7509fe2e0..0bb46793dcd4 100644
--- a/tools/testing/selftests/user_events/ftrace_test.c
+++ b/tools/testing/selftests/user_events/ftrace_test.c
@@ -261,6 +261,12 @@ TEST_F(user, register_events) {
ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSREG, ®));
ASSERT_EQ(0, reg.write_index);
+ /* Register without separator spacing should still match */
+ reg.enable_bit = 29;
+ reg.name_args = (__u64)"__test_event u32 field1;u32 field2";
+ ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSREG, ®));
+ ASSERT_EQ(0, reg.write_index);
+
/* Multiple registers to same name but different args should fail */
reg.enable_bit = 29;
reg.name_args = (__u64)"__test_event u32 field1;";
@@ -288,6 +294,8 @@ TEST_F(user, register_events) {
ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSUNREG, &unreg));
unreg.disable_bit = 30;
ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSUNREG, &unreg));
+ unreg.disable_bit = 29;
+ ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSUNREG, &unreg));
/* Delete should have been auto-done after close and unregister */
close(self->data_fd);
--
2.43.0
next prev parent reply other threads:[~2024-05-03 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 22:50 [for-linus][PATCH 0/9] tracing/tracefs: Fixes for v6.9 Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 1/9] tracing/user_events: Fix non-spaced field matching Steven Rostedt
2024-05-03 22:50 ` Steven Rostedt [this message]
2024-05-03 22:50 ` [for-linus][PATCH 3/9] eventfs/tracing: Add callback for release of an eventfs_inode Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 4/9] eventfs: Free all of the eventfs_inode after RCU Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 5/9] tracefs: Reset permissions on remount if permissions are options Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 6/9] tracefs: Still use mount point as default permissions for instances Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 7/9] eventfs: Do not differentiate the toplevel events directory Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 8/9] eventfs: Do not treat events directory different than other directories Steven Rostedt
2024-05-03 22:50 ` [for-linus][PATCH 9/9] eventfs: Have "events" directory get permissions from its parent Steven Rostedt
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=20240503225033.758019899@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=beaub@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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