Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: c/r rebase to 2.6.33-rc5
Date: Thu, 4 Feb 2010 19:40:09 -0600	[thread overview]
Message-ID: <20100205014009.GA5474@us.ibm.com> (raw)
In-Reply-To: <4B6B04E7.9080704-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>

Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> 
> I rebased the most recent patchset to 2.6.33, and pushed to
> ckpt-v19-rc2.10. only x86-32 is (lightly) tested.
> 
> it does not include patches from 1/27 and on. working on it
> now.
> 
> please review:
> 
> * arch-specific parts that I didn't screw up anything.
> btw, I moved checkpoint code from mm/ to kernel/
> 
> * [dan] network: net/checkpoint.c now uses sock_alloc_file();
> there may or may not be a leak of sock_hold().
> 
> * [serge] selinux now auto-generates some include files, see
> the changes to classmap.h
> 
> Oren.

For x86-64, I needed the following patch.  With this patch, only
the fileio and futex tests failed.  Suka is looking into the fileio
failure - Matt you might check the futex tests on whatever arch
you have available...

For s390, I of course still need
"fix 31-bit s390 checkpoint/restart wrappers" for compile with
CONFIG_COMPAT to succeed.

-serge

From 983e6674a72f0f911caddb3304c5d6a8e2e5d354 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Date: Thu, 4 Feb 2010 13:35:15 -0600
Subject: [PATCH 1/1] fix x86-64 checkpoint and restart syscall numbers

Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
---
 arch/x86/include/asm/unistd_64.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/include/asm/unistd_64.h b/arch/x86/include/asm/unistd_64.h
index fbac07d..17bacfd 100644
--- a/arch/x86/include/asm/unistd_64.h
+++ b/arch/x86/include/asm/unistd_64.h
@@ -665,9 +665,9 @@ __SYSCALL(__NR_perf_event_open, sys_perf_event_open)
 __SYSCALL(__NR_recvmmsg, sys_recvmmsg)
 #define __NR_eclone                   		300
 __SYSCALL(__NR_eclone, stub_eclone)
-#define __NR_checkpoint                   	300
+#define __NR_checkpoint                   	301
 __SYSCALL(__NR_checkpoint, stub_checkpoint)
-#define __NR_restart                   		301
+#define __NR_restart                   		302
 __SYSCALL(__NR_restart, stub_restart)
 
 #ifndef __NO_STUBS
-- 
1.6.0.6

  parent reply	other threads:[~2010-02-05  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 17:33 c/r rebase to 2.6.33-rc5 Oren Laadan
     [not found] ` <4B6B04E7.9080704-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-05  1:40   ` Serge E. Hallyn [this message]
     [not found]     ` <20100205014009.GA5474-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-05 14:45       ` Oren Laadan
     [not found]         ` <4B6C2EFA.3050703-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-05 14:57           ` Serge E. Hallyn
     [not found]             ` <20100205145722.GA6685-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-05 16:33               ` Serge E. Hallyn

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=20100205014009.GA5474@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@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