Date: Tue, 12 Feb 2008 11:28:49 -0600
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: clg@fr.ibm.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xemul@openvz.org,
       serue@us.ibm.com
Subject: Re: [patch 0/3] clone64() and unshare64() syscalls
Message-ID: <20080212172849.GB12177@sergelap.austin.ibm.com>
References: <20080211095806.585883882@fr.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080211095806.585883882@fr.ibm.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1256
Lines: 33

Quoting clg@fr.ibm.com (clg@fr.ibm.com):
> yet another try to extend the clone flags and probably not the last !
> 
> This patchset adds 2 new syscalls :
> 
>      long sys_clone64(unsigned long flags_high, unsigned long flags_low,
> 		unsigned long newsp);
> 
>      long sys_unshare64(unsigned long flags_high, unsigned long flags_low);
> 
> The current version of clone64() does not support CLONE_PARENT_SETTID and 
> CLONE_CHILD_CLEARTID because we would exceed the 6 registers limit of some 
> arches. It's possible to get around this limitation but we might not
> need it as we already have clone()
> 
> This is work in progress but already includes support for x86, x86_64, 
> x86_64(32), ppc64, ppc64(32), s390x, s390x(31). 
> 
> ia64 already supports 64bits clone flags through the clone2() syscall.
> should we harmonize the name to clone2 ?  
> 
> 
> Please see the changelog below.

Tested unshare64 with a new namespace using the first clone_hi bit, no
problems here (on a kvm-qemu image).

-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/