netdev - Re: Move an interface to init

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]

Message-ID: <87hao9elok.fsf@xmission.com>
Date:	Wed, 28 Nov 2012 10:28:43 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	David Shwatrz <dshwatrz@...il.com>
Cc:	Renato Westphal <renatowestphal@...il.com>, netdev@...r.kernel.org
Subject: Re: Move an interface to init_ne

David Shwatrz <dshwatrz@...il.com> writes:

> But when I run "modprobe 8139too" on namespace1, a device named "eth1"
> is created on the initial network namespace and not on namesapce1.
> I expected that in such a case, a device named "eth0" will be created
> on namespace1, since it was called from namespace1. Or maybe modprobe
> does
> not consider the namespace from which it was called ?

modprobe has no concept of the namespace from which it was called.

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