From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/3] syscalls/tgkill01: add new test
Date: Fri, 15 Mar 2019 11:08:24 +0100 [thread overview]
Message-ID: <20190315100824.GA5383@rei> (raw)
In-Reply-To: <CAFA6WYPx3fZ8Q2gR1wKi9=i0ML0JT8oPVebzaL03TFbxgxKiTg@mail.gmail.com>
Hi!
> >> int tst_checkpoint_wait(unsigned int id, unsigned int msec_timeout)
> >> {
> >> struct timespec timeout;
> >> + int ret;
> >>
> >> if (id >= tst_max_futexes) {
> >> errno = EOVERFLOW;
> >> @@ -94,8 +95,12 @@ int tst_checkpoint_wait(unsigned int id, unsigned int msec_timeout)
> >> timeout.tv_sec = msec_timeout/1000;
> >> timeout.tv_nsec = (msec_timeout%1000) * 1000000;
> >>
> >> - return syscall(SYS_futex, &tst_futexes[id], FUTEX_WAIT,
> >> - tst_futexes[id], &timeout);
> >> + do {
> >> + ret = syscall(SYS_futex, &tst_futexes[id], FUTEX_WAIT,
> >> + tst_futexes[id], &timeout);
> >
> > if (ret == -1 && errno == EINTR)
> > tst_res(TWARN | TERRNO, "FUTEX_WAIT operation was interrupted by a signal, retry again");
> >
>
> I am not sure if this warning message is desired for test-cases which
> needs to wait on checkpoints irrespective of signals like this
> tgkill01 test-case.
Agreed, it's not an error condition, it's just a coincidence that most
of the tests does not get signals when they sleep on futex, otherwise
thing would crash and burn. So I would argue that retrying on EINTR is
actually a bug fix rather than anything else.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-03-15 10:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 6:12 [LTP] [PATCH v2 0/3] syscalls: add tgkill test-cases Sumit Garg
2019-03-13 6:12 ` [LTP] [PATCH v2 1/3] syscalls/tgkill01: add new test Sumit Garg
2019-03-14 12:22 ` Cyril Hrubis
2019-03-14 13:25 ` Sumit Garg
2019-03-14 13:58 ` Cyril Hrubis
2019-03-15 7:45 ` Li Wang
2019-03-15 9:22 ` Sumit Garg
2019-03-15 10:08 ` Cyril Hrubis [this message]
2019-03-15 10:23 ` Li Wang
2019-03-15 11:33 ` Cyril Hrubis
2019-03-18 6:39 ` Li Wang
2019-03-15 9:15 ` Sumit Garg
2019-03-15 10:18 ` Cyril Hrubis
2019-03-15 14:01 ` Sumit Garg
2019-03-18 12:59 ` Cyril Hrubis
2019-03-13 6:12 ` [LTP] [PATCH v2 2/3] syscalls/tgkill02: " Sumit Garg
2019-03-13 6:12 ` [LTP] [PATCH v2 3/3] syscalls/tgkill03: " Sumit Garg
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=20190315100824.GA5383@rei \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.