netdev - Re: named network namespace -- setns() with Invalid argument (errno 22)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 30 Oct 2013 13:54:55 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	dilip.daya@...com
Cc:	netdev@...r.kernel.org
Subject: Re: named network namespace -- setns() with Invalid argument (errno 22)

ebiederm@...ssion.com (Eric W. Biederman) writes:

> Dilip Daya <dilip.daya@...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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html