Hi,

this should fix a regression in kill05.

Why did tst_resm/tst_exit get replaced by perror/exit in 84f181fd?


Signed-off-by: Cristian Greco <[email protected]>
---
 testcases/kernel/syscalls/kill/kill05.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/testcases/kernel/syscalls/kill/kill05.c
b/testcases/kernel/syscalls/kill/kill05.c index 0193100..ac5dc86 100644
--- a/testcases/kernel/syscalls/kill/kill05.c
+++ b/testcases/kernel/syscalls/kill/kill05.c
@@ -121,11 +121,12 @@ int main(int ac, char **av)
                tst_brkm(TBROK, cleanup, "Fork failed");
        else if (pid == 0)
                do_master_child(av);
-
+  else {
        if (waitpid(pid, &status, 0) == -1)
                tst_resm(TBROK|TERRNO, "waitpid failed");
        else if (!WIFEXITED(status) || WEXITSTATUS(status) != 0)
                tst_resm(TFAIL, "child exited abnormally");
+  }
        cleanup();
        tst_exit();
 }
-- 
1.7.4.1


Thanks,
--
Cristian Greco
GPG key ID: 0xCF4D32E4

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to