From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] network/echoes: fix endless loop on error
Date: Tue, 6 Dec 2016 13:53:14 +0300 [thread overview]
Message-ID: <5846989A.2020104@oracle.com> (raw)
In-Reply-To: <20161129160259.31058-1-pvorel@suse.cz>
Hi,
On 11/29/2016 07:02 PM, Petr Vorel wrote:
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> testcases/network/tcp_cmds/echo/echoes.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/testcases/network/tcp_cmds/echo/echoes.c b/testcases/network/tcp_cmds/echo/echoes.c
> index 8138d28..d753d98 100644
> --- a/testcases/network/tcp_cmds/echo/echoes.c
> +++ b/testcases/network/tcp_cmds/echo/echoes.c
> @@ -97,6 +97,7 @@ int main(int argc, char *argv[], char *env[])
>
> if ((pid = wait(&wait_stat)) == -1)
> tst_resm(TFAIL | TERRNO, "wait failed");
> +
> if (wait_stat == 0) {
> for (j = 0; j < i; j++) {
> if (echo_struc[j].pid == pid) {
> @@ -105,7 +106,6 @@ int main(int argc, char *argv[], char *env[])
> }
> }
> } else {
> -
> tst_resm(TFAIL, "wait(2) status was non-zero");
>
> if (WIFEXITED(wait_stat)) {
> @@ -120,6 +120,9 @@ int main(int argc, char *argv[], char *env[])
> if (kill(echo_struc[k].pid, 0) == 0) {
> kill(echo_struc[k].pid, 9);
> }
> + if (echo_struc[k].pid == pid) {
> + finish--;
> + }
Good catch, looks like we could substitute the while loop here with
tst_reap_children() library function and remove "echo_struc" as well?
Thanks,
Alexey
next prev parent reply other threads:[~2016-12-06 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:02 [LTP] [PATCH 1/1] network/echoes: fix endless loop on error Petr Vorel
2016-12-06 10:53 ` Alexey Kodanev [this message]
2016-12-06 13:58 ` Petr Vorel
2016-12-14 17:06 ` Petr Vorel
2016-12-15 11:48 ` Alexey Kodanev
[not found] ` <20161215115111.srk5fmrehsllbhuw@x230>
2016-12-15 12:12 ` Alexey Kodanev
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=5846989A.2020104@oracle.com \
--to=alexey.kodanev@oracle.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 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.