From: Suzuki Poulose <suzuki@in.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP : Fix connectors event_generator program : gen_fork
Date: Wed, 09 Sep 2009 10:48:40 +0530 [thread overview]
Message-ID: <4AA73AB0.9020202@in.ibm.com> (raw)
In-Reply-To: <4AA7391B.4020804@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Li Zefan wrote:
> Suzuki Poulose wrote:
>> Hi,
>>
>> There is a testcase issue in the event_generator code. The gen_fork() is
>> called to generate the fork event.
>>
>> The child process prints the following message:
>>
>> static inline void gen_fork(void)
>> {
>> pid_t pid;
>> int status;
>>
>> pid = fork();
>> if (pid == 0) {
>> printf("fork parent: %d, child: %d\n", getppid(),
>> getpid());
>> exit(0);
>> } else if (pid < 0) {
>> fprintf(stderr, "fork() failed\n");
>> exit(1);
>> }
>> }
>>
>> Now the parent process just exits after this call. So, if the child
>> doesn't get to run before parent exits, the child will see the ppid as
>> 1, that of INIT and this contradicts the actual data. Hence the test fails.
>>
>> Attached patch fixes the issue. I have verified the same. Please apply.
>>
>
> Thanks for fixing it.
>
> Acked-by: Li Zefan <lizf@cn.fujitsu.com>
>
> But you forgot to add your Signed-off-by in the patch. ;)
>
Ah! Thanks for catching that ! Re-attaching it ;)
Thanks
Suzuki
[-- Attachment #2: connectors-gen_fork-wait-for-child.diff --]
[-- Type: text/plain, Size: 1047 bytes --]
gen_fork() event should wait until the child exits. Otherwise the child would see INIT as the parent and
end up in collecting wrong information to compare with.
Signed-off-by: Suzuki K P <suzuki@in.ibm.com>
Acked-by: Li Zefan <lizf@cn.fujitsu.com>
Index: ltp/testcases/kernel/connectors/pec/event_generator.c
===================================================================
--- ltp.orig/testcases/kernel/connectors/pec/event_generator.c 2008-10-22 13:40:31.000000000 +0000
+++ ltp/testcases/kernel/connectors/pec/event_generator.c 2009-09-08 13:52:14.000000000 +0000
@@ -25,6 +25,9 @@
#include <stdlib.h>
#include <stdio.h>
#include <pwd.h>
+#include <sys/types.h>
+#include <sys/wait.h>
+
#include "test.h"
#define DEFAULT_EVENT_NUM 1
@@ -94,6 +97,7 @@
static inline void gen_fork(void)
{
pid_t pid;
+ int status;
pid = fork();
if (pid == 0) {
@@ -102,6 +106,8 @@
} else if (pid < 0) {
fprintf(stderr, "fork() failed\n");
exit(1);
+ } else { /* Parent should wait for the child */
+ wait(&status);
}
}
[-- Attachment #3: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-09-09 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 15:49 [LTP] LTP : Fix connectors event_generator program : gen_fork Suzuki Poulose
2009-09-09 5:11 ` Li Zefan
2009-09-09 5:18 ` Suzuki Poulose [this message]
2009-09-09 6:49 ` Subrata Modak
2009-09-09 21:31 ` 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=4AA73AB0.9020202@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=lizf@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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