From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [v10][PATCH 8/9] Define clone_with_pids() syscall
Date: Tue, 03 Nov 2009 08:16:20 -0800 [thread overview]
Message-ID: <1257264980.31972.2518.camel@nimitz> (raw)
In-Reply-To: <20091101204548.GG23168-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Sun, 2009-11-01 at 12:45 -0800, Sukadev Bhattiprolu wrote:
> +int sys_clone_with_pids(struct pt_regs *regs)
> +{
...
> + rc = copy_from_user(&kcs, ucs, sizeof(kcs));
> + if (rc)
> + return -EFAULT;
> +
> + /*
> + * TODO: If size of clone_args is not what the kernel expects, it
> + * could be that kernel is newer and has an extended structure.
> + * When that happens, this check needs to be smarter (and we
> + * need an additional copy_from_user()). For now, assume exact
> + * match.
> + */
> + if (kcs.clone_args_size != sizeof(kcs))
> + return -EINVAL;
> +
> + /*
> + * To avoid future compatibility issues, ensure unused fields are 0.
> + */
> + if (kcs.reserved1 || kcs.clone_flags_high)
> + return -EINVAL;
Suka, is there a reason we don't have these bits in some
arch-independent code? I would have thought the stuff in the
process_32.c code would be just as thin a wrapper as possible to unwrap
the pt_regs and call into generic code.
-- Dave
next prev parent reply other threads:[~2009-11-03 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 20:41 [v10][PATCH] Implement clone_with_pids() syscall Sukadev Bhattiprolu
[not found] ` <20091101204132.GA22116-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-01 20:42 ` [v10][PATCH 1/9] Factor out code to allocate pidmap page Sukadev Bhattiprolu
2009-11-01 20:43 ` [v10][PATCH 2/9] Have alloc_pidmap() return actual error code Sukadev Bhattiprolu
2009-11-01 20:44 ` [v10][PATCH 3/9] Define set_pidmap() function Sukadev Bhattiprolu
2009-11-01 20:44 ` [v10][PATCH 4/9] Add target_pids parameter to alloc_pid() Sukadev Bhattiprolu
2009-11-01 20:44 ` [v10][PATCH 5/9] Add target_pids parameter to copy_process() Sukadev Bhattiprolu
2009-11-01 20:45 ` [v10][PATCH 6/9] Check invalid clone flags Sukadev Bhattiprolu
2009-11-01 20:45 ` [v10][PATCH 7/9] Define do_fork_with_pids() Sukadev Bhattiprolu
2009-11-01 20:45 ` [v10][PATCH 8/9] Define clone_with_pids() syscall Sukadev Bhattiprolu
[not found] ` <20091101204548.GG23168-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-02 18:09 ` Oren Laadan
[not found] ` <4AEF2077.5080107-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-11-03 6:44 ` Sukadev Bhattiprolu
[not found] ` <20091103064454.GA22483-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-03 8:46 ` Arnd Bergmann
2009-11-03 16:16 ` Dave Hansen [this message]
2009-11-03 17:16 ` Sukadev Bhattiprolu
2009-11-04 0:32 ` Sukadev Bhattiprolu
2009-11-01 20:46 ` [v10][PATCH 9/9] Document " Sukadev Bhattiprolu
2009-11-02 18:10 ` [v10][PATCH] Implement " Oren Laadan
[not found] ` <4AEF207F.3000904-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-11-02 20:17 ` Sukadev Bhattiprolu
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=1257264980.31972.2518.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.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