public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sunliming <sunliming@kylinos.cn>
To: rostedt@goodmis.org, mhiramat@kernel.org, beaub@linux.microsoft.com
Cc: kelulanainsley@gmail.com, linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org, sunliming <sunliming@kylinos.cn>
Subject: [PATCH v3 3/3] selftests/user_events: Add test cases when event is diabled
Date: Wed, 21 Jun 2023 14:35:02 +0800	[thread overview]
Message-ID: <20230621063502.154378-1-sunliming@kylinos.cn> (raw)

When user_events are disabled, it's write operation should return zero.
Add this test cases.

Signed-off-by: sunliming <sunliming@kylinos.cn>
---
 tools/testing/selftests/user_events/ftrace_test.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tools/testing/selftests/user_events/ftrace_test.c b/tools/testing/selftests/user_events/ftrace_test.c
index d33bd31425db..7968d69c3a5c 100644
--- a/tools/testing/selftests/user_events/ftrace_test.c
+++ b/tools/testing/selftests/user_events/ftrace_test.c
@@ -297,6 +297,9 @@ TEST_F(user, write_events) {
 	io[0].iov_base = &reg.write_index;
 	io[0].iov_len = sizeof(reg.write_index);
 
+	/* Write should return zero when event is not enabled */
+	ASSERT_EQ(0, writev(self->data_fd, (const struct iovec *)io, 3));
+
 	/* Enable event */
 	self->enable_fd = open(enable_file, O_RDWR);
 	ASSERT_NE(-1, write(self->enable_fd, "1", sizeof("1")))
-- 
2.25.1


             reply	other threads:[~2023-06-21  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  6:35 sunliming [this message]
2023-06-22 20:27 ` [PATCH v3 3/3] selftests/user_events: Add test cases when event is diabled Beau Belgrave
2023-06-22 20:30   ` Steven Rostedt
2023-06-22 20:50     ` Beau Belgrave

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=20230621063502.154378-1-sunliming@kylinos.cn \
    --to=sunliming@kylinos.cn \
    --cc=beaub@linux.microsoft.com \
    --cc=kelulanainsley@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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