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] Skip down interfaces (v2)
Date: Thu, 01 Apr 2010 08:49:53 -0700 [thread overview]
Message-ID: <87sk7fcgv2.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <4BB4BA26.1050707-VXdhtT5mjnY@public.gmane.org> (Brian Haley's message of "Thu\, 01 Apr 2010 11\:22\:14 -0400")
BH> But devices that are not IFF_UP can still have addresses
BH> associated with them, wouldn't this cause those addresses to not
BH> be checkpointed?
Yes. This was discussed on IRC a bit as being a reasonable
compromise. Right now, there are several pernet devices that could
show up in a new network namespace that will prevent a checkpoint from
completing. Since you can't easily, and at runtime, get rid of these
devices without recompiling the kernel, you're kinda stuck. So, we
discussed this as something that will let you out of that situation
for interfaces that are down.
We could, I suppose, inspect the interfaces a bit to see if they have
any addresses configured before we agree to skip them. However, that
could falsely trigger a failure because of autoconf addresses, I would
think.
The plan is to have a "strict mode" flag that will attempt to
checkpoint and fail on down but unsupported interfaces to make sure we
don't save an inaccurate representation of the netns that the
application is in.
--
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
prev parent reply other threads:[~2010-04-01 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 16:23 [PATCH] Skip down interfaces (v2) Dan Smith
[not found] ` <1270052634-8170-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-31 16:50 ` Serge E. Hallyn
2010-04-01 4:43 ` Oren Laadan
2010-04-01 4:45 ` Oren Laadan
2010-04-01 15:22 ` Brian Haley
[not found] ` <4BB4BA26.1050707-VXdhtT5mjnY@public.gmane.org>
2010-04-01 15:37 ` Serge E. Hallyn
2010-04-01 15:49 ` Dan Smith [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=87sk7fcgv2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.