The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Louis Rilling <Louis.Rilling@kerlabs.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Containers <containers@lists.linux-foundation.org>,
	Nathan Lynch <nathanl@austin.ibm.com>,
	linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	hpa@zytor.com, mingo@elte.hu, torvalds@linux-foundation.org,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Pavel Emelyanov <xemul@openvz.org>
Subject: Re: [RFC][v7][PATCH 8/9]: Define clone2() syscall
Date: Fri, 25 Sep 2009 10:23:47 +0200	[thread overview]
Message-ID: <20090925082346.GB4436@localdomain> (raw)
In-Reply-To: <200909242343.59903.arnd@arndb.de>

[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]

On Thu, Sep 24, 2009 at 11:43:59PM +0200, Arnd Bergmann wrote:
> On Thursday 24 September 2009, Sukadev Bhattiprolu wrote:
> > +asmlinkage long
> > +sys_clone2(struct clone_struct __user *ucs, pid_t __user *pids)
> > +{
> > +       int rc;
> > +       struct clone_struct kcs;
> > +       unsigned long clone_flags;
> > +       int __user *parent_tid_ptr;
> > +       int __user *child_tid_ptr;
> > +       unsigned long __user child_stack_base;
> > +       struct pt_regs *regs;
> > +
> > +       rc = copy_from_user(&ucs, &kcs, sizeof(kcs));
> > +       if (rc)
> > +               return -EFAULT;
> > +
> > +       /*
> > +        * TODO: Convert clone_flags to 64-bit
> > +        */
> > +       clone_flags = (unsigned long)kcs.flags;
> > +       child_stack_base = (unsigned long)kcs.child_stack;
> > +       parent_tid_ptr = &ucs.parent_tid;
> > +       child_tid_ptr =  &ucs.child_tid;
> > +       regs = task_pt_regs(current);
> > +
> > +       if (!child_stack_base)
> > +               child_stack_base = user_stack_pointer(regs);
> > +
> > +       return do_fork_with_pids(clone_flags, child_stack_base, regs, 0,
> > +                       parent_tid_ptr, child_tid_ptr, kcs.nr_pids, pids);
> > +}
> > +
> 
> The function looks ok, but you have put it into arch/x86/kernel/process_32.c,
> which is specific to x86-32. Since the code in this form is generic, why
> not just put it into kernel/fork.c? You should probably enclose it within
> #ifdef CONFIG_HAVE_ARCH_TRACEHOOK to make sure that user_stack_pointer()
> is implemented, but then it would be immediately usable by the nine architectures
> implementing that. The other architectures can then decide between adding
> their private version of sys_clone2 with an open-coded user_stack_pointer
> implementation or alternatively implement the tracehooks.

It will very likely break ia64, which defines CONFIG_HAVE_ARCH_TRACEHOOK and
already has sys_clone2().

Louis

-- 
Dr Louis Rilling			Kerlabs
Skype: louis.rilling			Batiment Germanium
Phone: (+33|0) 6 80 89 08 23		80 avenue des Buttes de Coesmes
http://www.kerlabs.com/			35700 Rennes

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-25  8:23 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 16:55 [RFC][v7][PATCH 0/9] Implement clone2() system call Sukadev Bhattiprolu
2009-09-24 17:00 ` [RFC][v7][PATCH 1/9]: Factor out code to allocate pidmap page Sukadev Bhattiprolu
2009-09-24 17:00 ` [RFC][v7][PATCH 2/9]: Have alloc_pidmap() return actual error code Sukadev Bhattiprolu
2009-09-24 17:01 ` [RFC][v7][PATCH 3/9] Make pid_max a pid_ns property Sukadev Bhattiprolu
2009-09-24 17:45   ` Oren Laadan
2009-09-24 17:01 ` [RFC][v7][PATCH 4/9]: Add target_pid parameter to alloc_pidmap() Sukadev Bhattiprolu
2009-09-24 17:47   ` Oren Laadan
2009-09-24 17:01 ` [RFC][v7][PATCH 5/9]: Add target_pids parameter to alloc_pid() Sukadev Bhattiprolu
2009-09-24 17:02 ` [RFC][v7][PATCH 6/9]: Add target_pids parameter to copy_process() Sukadev Bhattiprolu
2009-09-24 17:02 ` [RFC][v7][PATCH 7/9]: Define do_fork_with_pids() Sukadev Bhattiprolu
2009-09-24 17:03 ` [RFC][v7][PATCH 8/9]: Define clone2() syscall Sukadev Bhattiprolu
2009-09-24 21:43   ` Arnd Bergmann
2009-09-25  8:23     ` Louis Rilling [this message]
2009-09-25 10:56       ` Louis Rilling
2009-09-29 18:05         ` Sukadev Bhattiprolu
2009-09-29 18:40           ` Roland McGrath
2009-09-29 18:44             ` H. Peter Anvin
2009-09-29 19:02               ` Arjan van de Ven
2009-09-29 19:10                 ` Linus Torvalds
2009-09-29 20:02                   ` H. Peter Anvin
2009-09-29 22:11                     ` Linus Torvalds
2009-09-29 22:19                       ` H. Peter Anvin
2009-09-30 16:15                         ` Arnd Bergmann
2009-09-30 16:27                           ` Linus Torvalds
2009-09-30 17:59                             ` Arnd Bergmann
2009-09-30 19:14                               ` Linus Torvalds
2009-09-30  6:48                       ` Roland McGrath
2009-09-29 20:00                 ` H. Peter Anvin
2009-09-29 21:58           ` Oren Laadan
2009-09-24 17:03 ` [RFC][v7][PATCH 9/9]: Document " Sukadev Bhattiprolu
2009-09-24 18:05   ` Randy Dunlap
2009-09-25  2:31   ` KOSAKI Motohiro
2009-09-24 17:44 ` [RFC][v7][PATCH 0/9] Implement clone2() system call Oren Laadan
2009-09-24 20:15   ` Sukadev Bhattiprolu
2009-09-24 22:06     ` Oren Laadan
2009-09-24 22:21       ` Arnd Bergmann
2009-09-24 23:19         ` Oren Laadan
2009-10-01  2:36   ` Sukadev Bhattiprolu
2009-10-01 15:19     ` Oren Laadan
2009-09-24 17:57 ` Alexey Dobriyan
2009-09-24 18:35   ` Serge E. Hallyn
2009-09-30  5:34     ` Alexey Dobriyan
2009-09-30 17:41       ` Oren Laadan
2009-10-02 20:27         ` Alexey Dobriyan
2009-10-02 21:06           ` Oren Laadan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090925082346.GB4436@localdomain \
    --to=louis.rilling@kerlabs.com \
    --cc=adobriyan@gmail.com \
    --cc=arnd@arndb.de \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nathanl@austin.ibm.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox