From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oren Laadan Subject: CLONE_PARENT in a container Date: Thu, 19 Mar 2009 18:32:57 -0400 Message-ID: <49C2C819.4070802@cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Linux Containers List-Id: containers.vger.kernel.org What happens when a container-init calls clone() with the CLONE_PARENT flag set ? Since CLONE_PARENT can be used to create a sibling, I'd think that this will create a sibling, in particular, a new task in the same container whose parent is the parent of the container. From a quick look in the code I can't see why this would be impossible. Is this so ? Is this the desired behavior ? Oren.