mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: mtk.manpages@gmail.com
Cc: Pavel Emelyanov <xemul@openvz.org>,
	Kir Kolyshkin <kir@openvz.org>,
	linux-man@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Sukadev Bhattiprolu <sukadev@us.ibm.com>,
	Nadia Derbey <Nadia.Derbey@bull.net>
Subject: Re: Documentation for CLONE_NEWPID
Date: Wed, 26 Nov 2008 11:08:51 -0600	[thread overview]
Message-ID: <20081126170851.GA24943@hallyn.com> (raw)
In-Reply-To: <cfd18e0f0811250709x4e2cc5cdhafb9ccf494890442@mail.gmail.com>

Quoting Michael Kerrisk (mtk.manpages@googlemail.com):
> Hi Serge,
> > I assume you've considered the pros and cons of mentioning
> > signal semantics with respect to init tasks of child pid namespaces,
> > and decided it's not worth mentioning yet as the semantics are not
> > yet finalized?
> >
> > The goal is to treat the process as a system-wide init with respect
> > to signals coming from its own namespace, and treat it as an ordinary
> > task for signals coming from its ancestor namespaces.  But as you've
> > probably read, the implementation may result in some unfortunate
> > side-effects regarding blocked signals etc.
> 
> No I haven't considered this at all.  Could you provide some pointers
> to relevant discussions on this?

The discussions are going on right now on lkml (see for instance
http://lkml.org/lkml/2008/11/15/124).  But I think Nadia has already
written something up.  Nadia, could you send what you have to
Michael?

thanks,
-serge

  reply	other threads:[~2008-11-26 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19  2:59 Michael Kerrisk
2008-11-23 22:20 ` Serge E. Hallyn
2008-11-25 15:09   ` Michael Kerrisk
2008-11-26 17:08     ` Serge E. Hallyn [this message]
2008-11-24 12:46 ` Pavel Emelyanov
2008-11-25 15:46   ` Michael Kerrisk
2008-11-25 15:54     ` Pavel Emelyanov
2008-11-25 16:27       ` Michael Kerrisk

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=20081126170851.GA24943@hallyn.com \
    --to=serge@hallyn.com \
    --cc=Nadia.Derbey@bull.net \
    --cc=kir@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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

all inboxes | Powered by JetHome®