public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: ebiederm@xmission•com (Eric W. Biederman)
To: dilip.daya@hp•com
Cc: netdev@vger•kernel.org
Subject: Re: named network namespace -- setns() with Invalid argument (errno 22)
Date: Wed, 30 Oct 2013 13:54:55 -0700	[thread overview]
Message-ID: <87wqku7a3k.fsf@xmission.com> (raw)
In-Reply-To: <8738njfkdp.fsf@xmission.com> (Eric W. Biederman's message of "Tue, 29 Oct 2013 21:33:22 -0700")

ebiederm@xmission•com (Eric W. Biederman) writes:

> Dilip Daya <dilip.daya@hp•com> writes:
>
>> Hi All,
>>
>> Is the following intended behavior for adding "nested" named network namespaces ?
>
> Not exactly intended but this is not misbehavior either.
>
> Mostly this is a don't do that then scenario.

Let me clarify a little. The primary purpose of ip netns exec is to
allow programs that are not aware or more than one network namespace
to work without modification.  It is not intended to be a primary
environment for applications to run in.

Which is a big part of where the don't do that then, comes from.

If you can figure out what is going on and send patches I will be happy
to accept them.

Also public conversation is appreciated so that anyone else with the
same confusions may be educated at the same time.


Eric

      reply	other threads:[~2013-10-30 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  0:16 named network namespace -- setns() with Invalid argument (errno 22) Dilip Daya
2013-10-30  4:33 ` Eric W. Biederman
2013-10-30 20:54   ` Eric W. Biederman [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=87wqku7a3k.fsf@xmission.com \
    --to=ebiederm@xmission$(echo .)com \
    --cc=dilip.daya@hp$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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