From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [user-cr PATCH 1/1] Fix x86-64 syscall numbers
Date: Fri, 25 Mar 2011 22:08:03 -0400 [thread overview]
Message-ID: <4D8D4A83.7070607@cs.columbia.edu> (raw)
In-Reply-To: <20110214164438.GA16666@localhost>
Hmm... this is because:
1) Need to s/clone_with_pids/eclone/ in scripts/extract-headers.sh, and
2) Properly run scripts/extracr-headers.sh before pushing user-cr.
Will do for v23-rc2.
Oren.
On 02/14/2011 11:44 AM, Serge E. Hallyn wrote:
> Signed-off-by: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> ---
> clone_x86_64.c | 2 +-
> include/linux/checkpoint.h | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/clone_x86_64.c b/clone_x86_64.c
> index 5a22093..6750786 100644
> --- a/clone_x86_64.c
> +++ b/clone_x86_64.c
> @@ -26,7 +26,7 @@
> #include "eclone.h"
>
> #ifndef __NR_eclone
> -#define __NR_eclone 300
> +#define __NR_eclone 303
> #endif
>
> int eclone(int (*fn)(void *), void *fn_arg, int clone_flags_low,
> diff --git a/include/linux/checkpoint.h b/include/linux/checkpoint.h
> index b6ac12d..3688ae1 100644
> --- a/include/linux/checkpoint.h
> +++ b/include/linux/checkpoint.h
> @@ -54,11 +54,11 @@
> #elif __x86_64__
>
> # ifndef __NR_checkpoint
> -# define __NR_checkpoint 301
> +# define __NR_checkpoint 304
> # endif
>
> # ifndef __NR_restart
> -# define __NR_restart 302
> +# define __NR_restart 305
> # endif
>
> #else
prev parent reply other threads:[~2011-03-26 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 16:44 [user-cr PATCH 1/1] Fix x86-64 syscall numbers Serge E. Hallyn
2011-03-26 2:08 ` Oren Laadan [this message]
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=4D8D4A83.7070607@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@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