From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] recvmsg01: kill child only if one was forked
Date: Tue, 08 Nov 2011 16:08:02 +0800 [thread overview]
Message-ID: <4EB8E362.1090602@cn.fujitsu.com> (raw)
In-Reply-To: <fd23b1ea-f8c6-45ba-8591-78444e165a36@zmail16.collab.prod.int.phx2.redhat.com>
On 11/08/2011 03:50 PM, Jan Stancek wrote:
>
>
> ----- Original Message -----
>> From: "Wanlong Gao" <gaowanlong@cn.fujitsu.com>
>> To: "Jan Stancek" <jstancek@redhat.com>
>> Cc: ltp-list@lists.sourceforge.net
>> Sent: Tuesday, November 8, 2011 8:21:01 AM
>> Subject: Re: [LTP] [PATCH] recvmsg01: kill child only if one was forked
>>
>> On 11/08/2011 03:14 PM, Jan Stancek wrote:
>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Wanlong Gao" <gaowanlong@cn.fujitsu.com>
>>>> To: "Jan Stancek" <jstancek@redhat.com>
>>>> Cc: ltp-list@lists.sourceforge.net
>>>> Sent: Tuesday, November 8, 2011 4:07:56 AM
>>>> Subject: Re: [LTP] [PATCH] recvmsg01: kill child only if one was
>>>> forked
>>>>
>>>> On 11/07/2011 08:53 PM, Jan Stancek wrote:
>>>>
>>>>>
>>>>> If start_server() fails, then pid will end up with -1 and
>>>>> cleanup() will do kill(-1, SIGKILL), which kills everything
>>>>> this process can kill.
>>>>>
>>>>> Change the test to kill pid (child) only when it successfully
>>>>> creates one.
>>>>>
>>>>
>>>>
>>>> Yeah, but this can't fix the problem in this case?
>>>>
>>>> recvmsg01 1 TBROK : server bind failed: errno=???(98):
>>>> Address
>>>> already in use
>>>> recvmsg01 2 TBROK : Remaining cases broken
>>>>
>>>
>>> I'm not sure I follow you here.
>>> In case you described start_server() returns -1,
>>> so pid = -1, and cleanup won't do kill(-1, SIGKILL).
>>>
>>
>>
>> Yeah, I understood you.
>>
>> But we wanna fix the case to TPASS but not TBROK, do we?
>
> True, but until we have such fix, we should at least make it
> less annoying when it fails.
>
>> So, I mean that the issues of this case is not only what you said.
>
> I didn't actually get to see yet what those are, because those
> TBROK messages didn't make it to log:
>
> <<<test_start>>>
> tag=recvmsg01 stime=1320555319
> cmdline="recvmsg01"
> contacts=""
> analysis=exit
> <<<test_output>>>
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=signaled termination_id=9 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>
>
> Regards,
> Jan
>
You can do like this:
while [ $? -eq 0 ]; do ./recvmsg01; done
Then you can see the TBROK message.
-Wanlong Gao
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2011-11-08 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 12:53 [LTP] [PATCH] recvmsg01: kill child only if one was forked Jan Stancek
2011-11-08 3:07 ` Wanlong Gao
2011-11-08 7:14 ` Jan Stancek
2011-11-08 7:21 ` Wanlong Gao
2011-11-08 7:50 ` Jan Stancek
2011-11-08 8:08 ` Wanlong Gao [this message]
2011-11-16 14:24 ` 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=4EB8E362.1090602@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jstancek@redhat.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