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:37:24 -0600	[thread overview]
Message-ID: <20100212193724.GA23537@us.ibm.com> (raw)
In-Reply-To: <364299f41002121123t25450771i262fd5a2250ed20a@mail.gmail.com>

Quoting Garrett Cooper (yanegomi@gmail.com):
> On Fri, Feb 12, 2010 at 11:17 AM, Garrett Cooper <yanegomi@gmail.com> wrote:
> > On Fri, Feb 12, 2010 at 9:51 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> >> Right, the test is checking whether kill -1 inside a private pidns
> >> kills all processes besides init in the pid namespace.
> >
> > Yeah, that's just not smart...
> >
> >>> 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.
> >
> > No, it isn't. If the test is being run as root it'll force a reboot on the box:
> >
> >     If pid is -1:
> >             If the user has super-user privileges, the signal is sent to all
> >             processes excluding system processes (with P_SYSTEM flag set),
> >             process with ID 1 (usually init(8)), and the process sending the
> >             signal.  If the user is not the super user, the signal is sent to
> >             all processes with the same uid as the user excluding the process
> >             sending the signal.  No error is returned if any process could be
> >             signaled.
> 
> Oh wait.. containers isolate PIDs and resources, correct (a weak form

weak?  :)

> of BSD jails or Solaris zones)? If so, then I'd watch the console //
> /var/log/messages, etc and see whether or not things stay alive after
> the signal is tossed...

Right.  To approximate this testcase by hand I just tried on today's
fresh kernel git pull

	ns_exec -cp /bin/bash
	for i in `seq 1 100`; do sleep 30 & done
	kill -USR1 -1

and only the sleeps were killed.

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

  reply	other threads:[~2010-02-12 19:37 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 [this message]
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=20100212193724.GA23537@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.