From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ptrace/ptrace05: preventing kill other processes if fork failed
Date: Tue, 12 Apr 2016 21:19:05 +0800 [thread overview]
Message-ID: <20160412131905.GD17476@localhost.localdomain> (raw)
In-Reply-To: <20160412100858.GC24915@rei.lan>
On Tue, Apr 12, 2016 at 12:08:59PM +0200, Cyril Hrubis wrote:
> Hi!
> > If fork failed, we should try next signum. Or the kill(-1, 9) on line
> > 196 will kill a lot of processes.
> >
> > Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
> > ---
> > testcases/kernel/syscalls/ptrace/ptrace05.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/testcases/kernel/syscalls/ptrace/ptrace05.c b/testcases/kernel/syscalls/ptrace/ptrace05.c
> > index d610cc0..e717319 100644
> > --- a/testcases/kernel/syscalls/ptrace/ptrace05.c
> > +++ b/testcases/kernel/syscalls/ptrace/ptrace05.c
> > @@ -99,7 +99,7 @@ int main(int argc, char **argv)
> > switch (child = fork()) {
> > case -1:
> > tst_resm(TBROK | TERRNO, "Failed to fork properly.");
> > - break;
> > + continue;
>
> I would just change this to tst_brkm(). There is no point in continuing
> the test if fork() starts failing.
>
Please review the new patch. Thanks.
From ee7ba40a79644a9039d0cc581f78e8708aef8b06 Mon Sep 17 00:00:00 2001
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
Date: Tue, 12 Apr 2016 09:13:57 +0800
Subject: [PATCH] ptrace/ptrace05: preventing kill other processes if fork
failed
If fork failed, we should try next signum. Or the kill(-1, 9) on line
196 will kill a lot of processes.
Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
---
testcases/kernel/syscalls/ptrace/ptrace05.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/syscalls/ptrace/ptrace05.c b/testcases/kernel/syscalls/ptrace/ptrace05.c
index d610cc0..db611e7 100644
--- a/testcases/kernel/syscalls/ptrace/ptrace05.c
+++ b/testcases/kernel/syscalls/ptrace/ptrace05.c
@@ -98,8 +98,8 @@ int main(int argc, char **argv)
switch (child = fork()) {
case -1:
- tst_resm(TBROK | TERRNO, "Failed to fork properly.");
- break;
+ tst_brkm(TBROK | TERRNO, NULL,
+ "Failed to fork properly.");
case 0:
if (ptrace(PTRACE_TRACEME, 0, NULL, NULL) != -1) {
--
1.9.3
next prev parent reply other threads:[~2016-04-12 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 3:07 [LTP] [PATCH] ptrace/ptrace05: preventing kill other processes if fork failed Han Pingtian
2016-04-12 10:08 ` Cyril Hrubis
2016-04-12 13:19 ` Han Pingtian [this message]
2016-04-12 15:42 ` 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=20160412131905.GD17476@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