All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net, Mitani <mitani@ryobi.co.jp>
Subject: Re: [LTP] "pidns17" problem in "2010-02-11" cvs
Date: Fri, 12 Feb 2010 13:41:14 -0600	[thread overview]
Message-ID: <20100212194114.GB23537@us.ibm.com> (raw)
In-Reply-To: <364299f41002121117i4fcc7b5bua47579a6ee2d661a@mail.gmail.com>

Quoting Garrett Cooper (yanegomi@gmail.com):
> On Fri, Feb 12, 2010 at 9:51 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Quoting Mitani (mitani@ryobi.co.jp):
> >> Hi,
> >>
> >> I tried to test with "2010-02-11" cvs in RHEL5.4 system.
> >> But the test brings termination of connection.
> >>
> >> I examined the phenomenon and discovered that "pidns17" test made
> >> accident and sshd stopped after the test.
> >>
> >>
> >> I had some problems.
> >>
> >> 1. I think that "tst_exit()" must be added last of "cleanup()"
> >>    function.
> >> ============
> >> --- ./testcases/kernel/containers/pidns/pidns17.c       2009-12-07
> >> 05:55:16.000000000 +0900
> >> +++ ./testcases/kernel/containers/pidns/pidns17.c.new   2010-02-12
> >> 16:26:31.000000000 +0900
> >> @@ -104,7 +104,6 @@
> >>
> >>         /* cleanup and exit */
> >>         CLEANUP();
> >> -       tst_exit();
> >>  }
> >>
> >>  /***********************************************************************
> >> @@ -136,7 +135,6 @@
> >>
> >>         /* cleanup and exit */
> >>         CLEANUP();
> >> -       tst_exit();
> >>  }      /* End main */
> >>
> >>  /*
> >> @@ -147,4 +145,5 @@
> >>  {
> >>         /* Clean the test testcase as LTP wants*/
> >>         TEST_CLEANUP;
> >> +       tst_exit();
> >>  }
> >
> > Yeah I'm afraid I don't understand what CLEANUP and tst_exit exactly
> > do.  Hopefully Garrett can give an educated answer.
> 
> Mitani's correct -- this is what should be done... CLEANUP is a
> constant that maps to cleanup in the event that tst_brkm is called,
> because linux_syscall_numbers.h's copy of syscall calls tst_brkm
> internally if ENOSYS is returned...

Cool, thanks

-serge

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2010-02-12 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  7:50 [LTP] "pidns17" problem in "2010-02-11" cvs Mitani
2010-02-12 17:51 ` Serge E. Hallyn
2010-02-12 19:17   ` Garrett Cooper
2010-02-12 19:23     ` Garrett Cooper
2010-02-12 19:37       ` Serge E. Hallyn
2010-02-12 19:41     ` Serge E. Hallyn [this message]

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=20100212194114.GB23537@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mitani@ryobi.co.jp \
    --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.