All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Mitani <mitani@ryobi.co.jp>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] "pidns17" problem in "2010-02-11" cvs
Date: Fri, 12 Feb 2010 11:51:25 -0600	[thread overview]
Message-ID: <20100212175125.GC15333@us.ibm.com> (raw)
In-Reply-To: <000001caabb7$fe895b60$fb9c1220$@co.jp>

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.

> ============
> 
> After revision, connection termination didn't occur.
> 
> 
> 2. I cannot understand the purpose that "kill()" function whose 
>    first parameter is "-1" is called.
> ------------
>         if (kill(-1, SIGUSR1) == -1) {
>                 tst_resm(TBROK | TERRNO, "cinit: kill(-1, SIGUSR1) failed");
>                 CLEANUP();
>         }
> ------------
> 
> If kill()'s first option is "-1", "man kill" says that
> "All processes with pid larger than 1 will be signaled."

Right, the test is checking whether kill -1 inside a private pidns
kills all processes besides init in the pid namespace.

> Therefore, not only the "sshd" but also the other processes were 
> affected, I think.

sshd is not in the private pid namespace and should not be killed.
If it is being killed by the pid -1 inside the container, then there
is a kernel bug.

> I'm glad if I could get some opinions.
> 
> 
> Thank you--
> 
> 
> -Tomonori Mitani

Thanks for testing.

-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

  reply	other threads:[~2010-02-12 17:51 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 [this message]
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

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