From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Dan Smith <danms@us.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] NetNS test fixes
Date: Fri, 7 May 2010 09:36:32 -0500 [thread overview]
Message-ID: <20100507143632.GC22099@us.ibm.com> (raw)
In-Reply-To: <877hnfyebf.fsf@caffeine.danplanet.com>
Quoting Dan Smith (danms@us.ibm.com):
> SM> Can you please ack this patch.
>
> Ack the revised one below instead :)
>
> By the way, these tests appear to start up sshd for no reason other
> than possibly checking that basic sockets work in the netns. Given
> the frailty and required setup of the "ftp" test, I think it would be
> better to replace it with a test using netcat and then yank the sshd
> bits from the ping tests.
Ack that.
> Dan Smith
> IBM Linux Technology Center
> email: danms@us.ibm.com
>
> NetNS test fixes (v2)
>
> This patch fixes a couple of netns test issues that cause invalid failures
> relating to exiting with a status variable that doesn't exist. It also
> fixes an instance of inverted logic and a failure to exec sshd with the
> full path (as required).
>
> Additionally, it makes the common child exec function more descriptive of
> what it tried to do and why it failed to ease debugging.
>
> Changes in v2:
> - Initialize status=0 at the top of child_1.sh to prevent overshadowing
> a (meaningless) sshd failure
>
> Signed-off-by: Dan Smith <danms@us.ibm.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
thanks,
-serge
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-05-07 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 17:43 [LTP] [PATCH] NetNS test fixes Dan Smith
2010-05-05 18:16 ` Subrata Modak
2010-05-07 9:41 ` Subrata Modak
2010-05-07 14:30 ` Dan Smith
2010-05-07 14:36 ` Serge E. Hallyn [this message]
2010-05-09 14:17 ` Subrata Modak
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=20100507143632.GC22099@us.ibm.com \
--to=serue@us.ibm.com \
--cc=danms@us.ibm.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