linux-kernel - Re: [patch 0/3] clone64() and unshare64() syscalls

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20080212172849.GB12177@sergelap.austin.ibm.com>
Date:	Tue, 12 Feb 2008 11:28:49 -0600
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	clg@...ibm.com
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	xemul@...nvz.org, serue@...ibm.com
Subject: Re: [patch 0/3] clone64() and unshare64() syscalls

Quoting clg@...ibm.com (clg@...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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/