All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Chris J Arges <chris.j.arges@canonical.com>
Cc: shemminger@osdl.org, netdev@vger.kernel.org
Subject: Re: iproute2: potential upgrade regression with 58a3e827
Date: Fri, 08 Nov 2013 14:42:20 -0800	[thread overview]
Message-ID: <87wqkiy0qb.fsf@xmission.com> (raw)
In-Reply-To: <527D65FB.8000407@canonical.com> (Chris J. Arges's message of "Fri, 08 Nov 2013 16:30:19 -0600")

Chris J Arges <chris.j.arges@canonical.com> writes:

> Fair enough. I really wanted to get a feel if this seemed like an actual
> bug, or rather it's behaving like we'd expect. I don't mind writing
> code, but I want to know if I'm hunting a bug, or adding a feature.

Making it ip netns add work reliably inside of ip netns exec and
handling all of the permutations is adding a feature.

Understanding why ip netns exec is failing in your specific case sounds
like there may be a missing error message.  Clearly you get into a
context where /var/run/netns/netns_old is no the bind mount we would
expect it to be.

I saw nothing that should unmake /var/run/netns/nnetns_old  as a mount
point.  So something strange is going on.

So you might want to go through and inspect to see what is happening.
Perhaps there is a missing error message somewhere.

Without understanding why that mountpoint fails to exist I can't say if
it is a real bug or if it just something weird caused by using an ip
netns exec it was not designed to be used and is known not to be 100%
robust in.

Eric

  reply	other threads:[~2013-11-08 22:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 18:03 iproute2: potential upgrade regression with 58a3e827 Chris J Arges
2013-11-08 21:36 ` Eric W. Biederman
2013-11-08 22:30   ` Chris J Arges
2013-11-08 22:42     ` Eric W. Biederman [this message]
2013-11-09 17:00 ` Brian Haley
2013-11-11 21:26   ` Chris J Arges
2013-11-11 21:38     ` Dilip Daya
2013-11-11 22:40       ` Eric W. Biederman
2013-11-12  0:36         ` Dilip Daya
2013-12-13 18:46           ` [PATCH] " Chris J Arges
2013-12-13 18:55             ` Stephen Hemminger

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=87wqkiy0qb.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=chris.j.arges@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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.