From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] eventfd06: add AIO support check
Date: Tue, 21 Jan 2025 10:26:11 +0100 [thread overview]
Message-ID: <20250121092611.GB894129@pevik> (raw)
In-Reply-To: <20250121082236.5247-1-liwang@redhat.com>
> Just like what we did for io_setup01.c to avoid ENOSYS error:
> eventfd06.c:140: TBROK: io_setup() failed: ENOSYS
> Signed-off-by: Li Wang <liwang@redhat.com>
> ---
> testcases/kernel/syscalls/eventfd/eventfd06.c | 2 ++
> 1 file changed, 2 insertions(+)
> diff --git a/testcases/kernel/syscalls/eventfd/eventfd06.c b/testcases/kernel/syscalls/eventfd/eventfd06.c
> index 7339dd471..46d7f73d3 100644
> --- a/testcases/kernel/syscalls/eventfd/eventfd06.c
> +++ b/testcases/kernel/syscalls/eventfd/eventfd06.c
> @@ -136,6 +136,8 @@ static void test_poll(void)
> static void setup(void)
> {
> TEST(io_setup(MAXEVENTS, &ctx));
> + if (TST_RET == -ENOSYS)
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Maybe to be safe to check also TST_RET?
if (TST_RET == -1 && TTERRNO == ENOSYS)
Maybe (after the release) we could add new macro to tst_test_macros.h
similar to TEST(), which would do test like this (variant of tst_syscall()
macro). We already have 10 tests which do this manually.
Kind regards,
Petr
> + tst_brk(TCONF | TRERRNO, "io_setup(): AIO not supported by kernel");
> if (TST_RET < 0)
> tst_brk(TBROK, "io_setup() failed: %s", tst_strerrno(-TST_RET));
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-01-21 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 8:22 [LTP] [PATCH] eventfd06: add AIO support check Li Wang
2025-01-21 9:26 ` Petr Vorel [this message]
2025-01-21 10:33 ` Li Wang
2025-01-21 11:13 ` Petr Vorel
2025-01-21 16:14 ` Cyril Hrubis
2025-01-22 1:50 ` Li Wang
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=20250121092611.GB894129@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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