From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: ckpt-v20-rc1
Date: Sun, 14 Mar 2010 23:33:05 -0400 [thread overview]
Message-ID: <4B9DAA71.2000808@cs.columbia.edu> (raw)
In-Reply-To: <20100315032347.GA4707-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge E. Hallyn wrote:
> Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
>> I pushed all the recent patches to ckpt-v19-dev (except for Matt's code
>> order series). It includes the recent post of netdev/netns.
>>
>> Feel free to yell if I left out your patch unjustifiably.
>>
>> Also pushed ckpt-v20-rc1 which is a clean patchset of the same and
>> also rebased to 2.6.33, lightly tested here.
>>
>> The goal is to get ckpt-v20 in 1-2 days and post the series on LKML
>> following up on Andrew's reply.
>>
>> Before that, I'd like to validate that there are no regressions, and
>> apply some netns/netdev cleanups (in particular, the kernel doesn't
>> compile when NETNS isn't configured)
>>
>> Let's give it a quick test drive.
>>
>> Oren.
>>
>
> hmm,
>
> ERROR: "ckpt_obj_lookup" [drivers/net/veth.ko] undefined!
> ERROR: "do_ckpt_msg" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_hdr_put" [drivers/net/veth.ko] undefined!
> ERROR: "checkpoint_obj" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_netdev_in_init_netns" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_write_buffer" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_write_obj" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_obj_lookup_add" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_netdev_base" [drivers/net/veth.ko] undefined!
> ERROR: "ckpt_hdr_put" [drivers/net/macvlan.ko] undefined!
> ERROR: "ckpt_write_buffer" [drivers/net/macvlan.ko] undefined!
> ERROR: "ckpt_write_obj" [drivers/net/macvlan.ko] undefined!
> ERROR: "ckpt_netdev_base" [drivers/net/macvlan.ko] undefined!
> ERROR: "ckpt_debug_level" [drivers/net/macvlan.ko] undefined!
Oh... I didn't test with kernel modules. This required export
symbol - will send a patch promptly.
Some (the last two) are because NETNS isn't configured ?
I'm a bit concerned that the netns/netdev patches were not given
enough prime time to filter compilation/config issues.
Dan: do you think they are ready for the coming patch bomb that
we intend to send to LKML ?
Oren.
next prev parent reply other threads:[~2010-03-15 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 2:48 ckpt-v20-rc1 Oren Laadan
[not found] ` <4B9DA00C.3000001-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-15 2:52 ` ckpt-v20-rc1 Oren Laadan
2010-03-15 3:23 ` ckpt-v20-rc1 Serge E. Hallyn
[not found] ` <20100315032347.GA4707-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-15 3:33 ` Oren Laadan [this message]
[not found] ` <4B9DAA71.2000808-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-03-15 3:38 ` ckpt-v20-rc1 Serge E. Hallyn
2010-03-15 4:58 ` [PATCH] c/r: export key symbols to enable c/r from kernel modules 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=4B9DAA71.2000808@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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