From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] waitpid/waitpid02: check if fork failed
Date: Tue, 12 Apr 2016 21:13:24 +0800 [thread overview]
Message-ID: <20160412131324.GC17476@localhost.localdomain> (raw)
In-Reply-To: <20160412100536.GB24915@rei.lan>
On Tue, Apr 12, 2016 at 12:05:36PM +0200, Cyril Hrubis wrote:
> Hi!
> > } else {
> > + if (pid < 0) {
> > + tst_brkm(TBROK|TERRNO, cleanup, "fork failed");
> > + }
>
> The check should be done right after the fork() and not in the else
> branch. Also there shoudln't be the curly braces around the tst_brkm()
> since it's just a signle line.
>
> Otherwise it's fine.
>
Thanks. This is the new patch.
From 9785b11acc164725a5e93766ec08d199831fd7e5 Mon Sep 17 00:00:00 2001
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
Date: Mon, 11 Apr 2016 23:46:34 +0800
Subject: [PATCH] waitpid/waitpid02: check if fork failed
Break the test if fork failed. Or this test case will kill a lot of
processes on the system.
Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
---
testcases/kernel/syscalls/waitpid/waitpid02.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/testcases/kernel/syscalls/waitpid/waitpid02.c b/testcases/kernel/syscalls/waitpid/waitpid02.c
index e5d7957..7d3a65c 100644
--- a/testcases/kernel/syscalls/waitpid/waitpid02.c
+++ b/testcases/kernel/syscalls/waitpid/waitpid02.c
@@ -88,6 +88,9 @@ int main(int argc, char **argv)
pid = FORK_OR_VFORK();
+ if (pid < 0)
+ tst_brkm(TBROK|TERRNO, cleanup, "fork failed");
+
if (pid == 0) {
#ifdef UCLINUX
self_exec(argv[0], "");
--
1.9.3
next prev parent reply other threads:[~2016-04-12 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 3:03 [LTP] [PATCH] waitpid/waitpid02: check if fork failed Han Pingtian
2016-04-12 10:05 ` Cyril Hrubis
2016-04-12 13:13 ` Han Pingtian [this message]
2016-04-12 13:31 ` 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=20160412131324.GC17476@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