Skip to content

clone64() and unshare64() syscalls

[email protected] lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3change clone_flags type to u64arch/alpha/kernel/process.c arch/arm/kernel/process.c arch/avr32/kernel/process.c +48 more+81 -810 replies
2/3add do_unshare()kernel/fork.c+6 -10 replies
3/3add the clone64() and unshare64() syscallsarch/powerpc/kernel/entry_32.S arch/powerpc/kernel/entry_64.S arch/powerpc/kernel/process.c +18 more+140 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [patch 0/3] clone64() and unshare64() syscalls

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.

C.