From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Brian Haley <brian.haley-VXdhtT5mjnY@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [PATCH 3/3] C/R: Basic support for network namespaces and devices
Date: Thu, 21 Jan 2010 07:37:52 -0800 [thread overview]
Message-ID: <87fx5zpiy7.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <4B5781DF.6050106-VXdhtT5mjnY@public.gmane.org> (Brian Haley's message of "Wed\, 20 Jan 2010 17\:21\:19 -0500")
BH> What about:
BH> 1. Multicast
BH> 2. Device config info (ipv4_devconf)
<snip>
BH> What about addr->ifa_flags and all the other elements like
BH> prefixlen, scope and label?
I thought I was covered by calling it "Basic support..." :)
I've added these to the list of TODOs and will cook those up once the
basic bits are in.
>> + if ((ret >= 0) && (ret != h->inet4_addrs)) {
>> + ret = -EBUSY;
>> + ckpt_err(ctx, ret,
>> + "Addresses on interface %s changed\n", dev->name);
>> + goto out;
>> + }
BH> This isn't guaranteed to catch every change to the address list,
BH> just that the number of addresses is the same, is there no way to
BH> hold a lock the whole time?
Yeah, there probably is. I'll take a look.
Thanks!
--
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
next prev parent reply other threads:[~2010-01-21 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 15:01 Network namespace and device support Dan Smith
[not found] ` <1263999673-11279-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-20 15:01 ` [PATCH 1/3] Expose rtnl_link_ops_get() Dan Smith
2010-01-20 15:01 ` [PATCH 2/3] Add a veth_get_peer() and veth_set_peer() functions Dan Smith
2010-01-21 9:24 ` David Miller
2010-01-20 15:01 ` [PATCH 3/3] C/R: Basic support for network namespaces and devices Dan Smith
[not found] ` <1263999673-11279-4-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-20 17:36 ` Serge E. Hallyn
2010-01-20 21:26 ` Oren Laadan
2010-01-21 15:38 ` Dan Smith
[not found] ` <878wbrpix6.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-01-21 16:14 ` Oren Laadan
2010-01-20 22:21 ` Brian Haley
[not found] ` <4B5781DF.6050106-VXdhtT5mjnY@public.gmane.org>
2010-01-21 15:37 ` Dan Smith [this message]
[not found] ` <87fx5zpiy7.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-01-21 16:08 ` 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=87fx5zpiy7.fsf@caffeine.danplanet.com \
--to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=brian.haley-VXdhtT5mjnY@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@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