From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V3 2/3] syscalls: select: Verify that data is available to read
Date: Tue, 20 Oct 2020 15:06:00 +0200 [thread overview]
Message-ID: <20201020130600.GA16294@yuki.lan> (raw)
In-Reply-To: <20201019101048.knbl2w3q2xev6ywc@vireshk-i7>
Hi!
> Maybe I haven't understood what you meant when you said this earlier:
>
> And the coverate in these tests is a bit lacking, we do not have a
> single tests that would send a data over a pipe to a fd select is
> watching and check that select was woken up by that. There is no such
> test in the pselect/ directory either.
>
> > Also I would like to be more specific. E.g. expecting specific return
> > instead of just non-zero and also making sure the right bits are enabled
> > in the fd sets.
>
> Something like this ?
This is much better, I suppose that we should as well check the
individual bits in the fd_sets to make it perfect.
> diff --git a/testcases/kernel/syscalls/select/select01.c b/testcases/kernel/syscalls/select/select01.c
> index e4b5caecbb10..4b33c0a01380 100644
> --- a/testcases/kernel/syscalls/select/select01.c
> +++ b/testcases/kernel/syscalls/select/select01.c
> @@ -38,12 +38,15 @@ static void run(unsigned int n)
> struct tcases *tc = &tests[n];
> struct timeval timeout;
> char buf;
> + int exp_ret = 1;
>
> timeout.tv_sec = 0;
> timeout.tv_usec = 100000;
>
> - if (tc->writefd)
> + if (tc->writefd) {
> SAFE_WRITE(0, *tc->writefd, &buf, sizeof(buf));
> + exp_ret++;
> + }
>
> TEST(do_select(*tc->nfds + 1, tc->readfds, tc->writefds, 0, &timeout));
>
> @@ -51,6 +54,8 @@ static void run(unsigned int n)
> tst_res(TFAIL | TTERRNO, "select() failed %s", tc->desc);
> else if (!TST_RET)
> tst_res(TFAIL, "select() timed out %s", tc->desc);
> + else if (TST_RET != exp_ret)
> + tst_res(TFAIL, "select() returned incorrect value: %s, expected: %d, got: %lu", tc->desc, exp_ret, TST_RET);
> else
> tst_res(TPASS, "select() passed %s", tc->desc);
> }
>
> --
> viresh
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-10-20 13:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 9:44 [LTP] [PATCH V3 1/3] syscalls: select: Merge few tests and migrate to new format Viresh Kumar
2020-09-08 9:44 ` [LTP] [PATCH V3 2/3] syscalls: select: Verify that data is available to read Viresh Kumar
2020-10-14 12:13 ` Cyril Hrubis
2020-10-19 10:10 ` Viresh Kumar
2020-10-20 13:06 ` Cyril Hrubis [this message]
2020-10-21 4:32 ` [LTP] [PATCH V4 " Viresh Kumar
2020-10-21 12:04 ` Cyril Hrubis
2020-10-22 4:54 ` Viresh Kumar
2020-10-22 10:13 ` Cyril Hrubis
2020-09-08 9:44 ` [LTP] [PATCH V3 3/3] syscalls: select: Rename select04.c to select02.c Viresh Kumar
2020-10-14 12:15 ` Cyril Hrubis
2020-10-19 11:37 ` Viresh Kumar
2020-10-20 13:06 ` Cyril Hrubis
2020-10-21 5:32 ` [LTP] [PATCH V2 4/4] syscalls: select: Add failure tests Viresh Kumar
2020-10-21 14:54 ` Cyril Hrubis
2020-10-06 7:59 ` [LTP] [PATCH V3 1/3] syscalls: select: Merge few tests and migrate to new format Viresh Kumar
2020-10-14 12:05 ` Cyril Hrubis
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=20201020130600.GA16294@yuki.lan \
--to=chrubis@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).