public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Emelyanov <xemul@openvz.org>,
	daniel@hozac.com, Nadia Derbey <Nadia.Derbey@bull.net>,
	clg@fr.ibm.com, Containers <containers@lists.osdl.org>,
	sukadev@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Signals to cinit
Date: Wed, 12 Nov 2008 13:06:55 -0600	[thread overview]
Message-ID: <20081112190655.GB8233@us.ibm.com> (raw)
In-Reply-To: <20081112181211.GC3230@us.ibm.com>

Quoting Sukadev Bhattiprolu (sukadev@linux.vnet.ibm.com):
> Serge E. Hallyn [serue@us.ibm.com] wrote:
> | Quoting Oleg Nesterov (oleg@redhat.com):
> | > > | Perhaps we can start with something like the patch below. Not that I like
> | > > | it very much though. We should really place this code under
> | > > | CONFIG_I_DO_CARE_ABOUT_NAMESPACES ;)
> | > >
> | > > CONFIG_PID_NS ?
> | > 
> | > Ah yes, we have it ;)
> | 
> | Except I believe all distros at this point enable CONFIG_PID_NS, so
> | I'm not sure it's the right thing to use.
> 
> But if they do enable CONFIG_PID_NS they would want the signals to
> behave correctly ? IIUC, the reason we want to the hide the code
> is that it is not clean i.e if its not experimental or error-prone,
> are there other reasons someone with CONFIG_PID_NS=y want to hide it ?

I was going to argue yes, but again following my reasoning to its
logical conclusion leads us to a config parameter being bad anyway.

So yeah, never mind.

-serge

  reply	other threads:[~2008-11-12 19:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081101180505.GA24268@us.ibm.com>
     [not found] ` <20081110173839.GA11121@redhat.com>
2008-11-10 19:32   ` Signals to cinit Oleg Nesterov
2008-11-10 23:27     ` sukadev
2008-11-12 14:52       ` Oleg Nesterov
2008-11-12 16:12         ` Oleg Nesterov
2008-11-12 16:49         ` Serge E. Hallyn
2008-11-12 18:12           ` Sukadev Bhattiprolu
2008-11-12 19:06             ` Serge E. Hallyn [this message]
2008-11-11  2:24     ` sukadev
2008-11-12 15:05       ` Oleg Nesterov
2008-11-12 19:04         ` Sukadev Bhattiprolu
2008-11-14 17:26           ` Oleg Nesterov
2008-11-12 16:53     ` Serge E. Hallyn
2008-11-13 19:10     ` Sukadev Bhattiprolu

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=20081112190655.GB8233@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=Nadia.Derbey@bull.net \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=daniel@hozac.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=sukadev@us.ibm.com \
    --cc=xemul@openvz.org \
    /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