From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] waitpid/waitpid03: break test if fork failed
Date: Wed, 13 Apr 2016 14:58:18 +0800 [thread overview]
Message-ID: <20160413065818.GF17476@localhost.localdomain> (raw)
In-Reply-To: <20160412155230.GB2917@rei.suse.cz>
On Tue, Apr 12, 2016 at 05:52:41PM +0200, Cyril Hrubis wrote:
> Hi!
> > - tst_resm(TFAIL, "cannot open fork #%d", ikids);
> > + tst_brkm(TBROK|TERRNO, cleanup,
> > + "cannot open fork #%d", ikids);
>
> I guess that we should kill any of the allready sleeping children at this point.
>
> If we move the pid[] array to be global we can create a kill_children()
> function to send a signal to all pids in pid[] that are > 0 and call it
> if fork fails with SIGKILL as well as from the main loop with the
> SIGTERM as well.
>
I think this one is better, please have a look. Thanks.
From aff8c1decee88bae37a8460ddce8d10a7a8f3d1a Mon Sep 17 00:00:00 2001
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
Date: Tue, 12 Apr 2016 11:12:28 +0800
Subject: [PATCH] waitpid/waitpid03: break test if fork failed
If continue after the fork failure, a lot of processes may be killed by
the kill() on line 125.
Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
---
testcases/kernel/syscalls/waitpid/waitpid03.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/testcases/kernel/syscalls/waitpid/waitpid03.c b/testcases/kernel/syscalls/waitpid/waitpid03.c
index 2599a92..7e9d45c 100644
--- a/testcases/kernel/syscalls/waitpid/waitpid03.c
+++ b/testcases/kernel/syscalls/waitpid/waitpid03.c
@@ -106,7 +106,16 @@ int main(int argc, char **argv)
if (DEBUG)
tst_resm(TINFO, "child # %d", ikids);
} else if (pid[ikids] == -1) {
- tst_resm(TFAIL, "cannot open fork #%d", ikids);
+ int i;
+
+ tst_resm(TBROK|TERRNO, "cannot open fork #%d",
+ ikids);
+
+ for (i = 1; i < ikids; i++)
+ kill(pid[i], 9);
+
+ cleanup();
+ tst_exit();
} else {
#ifdef UCLINUX
if (self_exec(argv[0], "d", ikids) < 0) {
--
1.9.3
next prev parent reply other threads:[~2016-04-13 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 13:22 [LTP] [PATCH] waitpid/waitpid03: break test if fork failed Han Pingtian
2016-04-12 15:52 ` Cyril Hrubis
2016-04-13 3:29 ` Han Pingtian
2016-04-13 12:51 ` Cyril Hrubis
2016-04-13 6:58 ` Han Pingtian [this message]
2016-04-13 12:55 ` Cyril Hrubis
2016-04-14 3:09 ` Han Pingtian
2016-04-19 11:34 ` 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=20160413065818.GF17476@localhost.localdomain \
--to=hanpt@linux.vnet.ibm.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