From: Peng Haitao <penght@cn.fujitsu.com>
To: yanegomi@gmail.com
Cc: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] exit_group01: fix error of using wrong TEST_RETURN
Date: Wed, 19 Jan 2011 15:23:36 +0800 [thread overview]
Message-ID: <4D369178.4010107@cn.fujitsu.com> (raw)
Hi Garrett,
"TEST_RETURN" should be replaced with "cpid".
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
---
.../kernel/syscalls/exit_group/exit_group01.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/syscalls/exit_group/exit_group01.c b/testcases/kernel/syscalls/exit_group/exit_group01.c
index 9280f0a..d7454b2 100644
--- a/testcases/kernel/syscalls/exit_group/exit_group01.c
+++ b/testcases/kernel/syscalls/exit_group/exit_group01.c
@@ -113,7 +113,7 @@ int main(int ac, char **av) {
cpid = fork(); //call exit_group()
if (cpid == -1) {
tst_brkm(TFAIL|TERRNO, cleanup, "fork failed");
- } else if (TEST_RETURN == 0) {
+ } else if (cpid == 0) {
sleep(5);
TEST(syscall(__NR_exit_group,4));
} else {
@@ -129,4 +129,4 @@ int main(int ac, char **av) {
}
cleanup();
tst_exit();
-}
\ No newline at end of file
+}
--
1.7.3.1
--
Best Regards,
Peng Haitao
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-01-19 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 7:23 Peng Haitao [this message]
2011-01-19 7:30 ` [LTP] [PATCH] exit_group01: fix error of using wrong TEST_RETURN Garrett Cooper
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=4D369178.4010107@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.com \
/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.