From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: c/r rebase to 2.6.33-rc5
Date: Fri, 05 Feb 2010 09:45:14 -0500 [thread overview]
Message-ID: <4B6C2EFA.3050703@cs.columbia.edu> (raw)
In-Reply-To: <20100205014009.GA5474-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge E. Hallyn wrote:
> 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.
Ok, fixed, and pushed to ckpt-v19-rc2.10.
If this is more or less ok, I'll change it to ckpt-v19-rc3 :)
Oren.
next prev parent reply other threads:[~2010-02-05 14:45 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
[not found] ` <20100205014009.GA5474-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-05 14:45 ` Oren Laadan [this message]
[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=4B6C2EFA.3050703@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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