linux-kernel - Re: Documentation for CLONE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 26 Nov 2008 11:08:51 -0600
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	mtk.manpages@...il.com
Cc:	Pavel Emelyanov <xemul@...nvz.org>, Kir Kolyshkin <kir@...nvz.org>,
	linux-man@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Sukadev Bhattiprolu <sukadev@...ibm.com>,
	Nadia Derbey <Nadia.Derbey@...l.net>
Subject: Re: Documentation for CLONE_NEWPID

Quoting Michael Kerrisk (mtk.manpages@...glemail.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/