From: Beau Belgrave <beaub@linux.microsoft.com>
To: sunliming <sunliming@kylinos.cn>
Cc: rostedt@goodmis.org, mhiramat@kernel.org,
kelulanainsley@gmail.com, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] selftests/user_events: Enable the event before write_fault test in ftrace self-test
Date: Thu, 22 Jun 2023 20:24:02 +0000 [thread overview]
Message-ID: <ZJSt4nDATIm9r8WR@CPC-beaub-VBQ1L.localdomain> (raw)
In-Reply-To: <20230621063438.154271-1-sunliming@kylinos.cn>
On Wed, Jun 21, 2023 at 02:34:38PM +0800, sunliming wrote:
> The user_event has not be enabled in write_fault test in ftrace
> self-test, Just enable it.
>
> Signed-off-by: sunliming <sunliming@kylinos.cn>
Good catch.
Acked-by: Beau Belgrave <beaub@linux.microsoft.com>
Thanks!
> ---
> tools/testing/selftests/user_events/ftrace_test.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/testing/selftests/user_events/ftrace_test.c b/tools/testing/selftests/user_events/ftrace_test.c
> index abfb49558a26..d33bd31425db 100644
> --- a/tools/testing/selftests/user_events/ftrace_test.c
> +++ b/tools/testing/selftests/user_events/ftrace_test.c
> @@ -373,6 +373,10 @@ TEST_F(user, write_fault) {
> ASSERT_EQ(0, ioctl(self->data_fd, DIAG_IOCSREG, ®));
> ASSERT_EQ(0, reg.write_index);
>
> + /* Enable event */
> + self->enable_fd = open(enable_file, O_RDWR);
> + ASSERT_NE(-1, write(self->enable_fd, "1", sizeof("1")))
> +
> /* Write should work normally */
> ASSERT_NE(-1, writev(self->data_fd, (const struct iovec *)io, 2));
>
> --
> 2.25.1
prev parent reply other threads:[~2023-06-22 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 6:34 [PATCH v3 2/3] selftests/user_events: Enable the event before write_fault test in ftrace self-test sunliming
2023-06-22 20:24 ` Beau Belgrave [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=ZJSt4nDATIm9r8WR@CPC-beaub-VBQ1L.localdomain \
--to=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 \
--cc=sunliming@kylinos.cn \
/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