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
| ||
|
Message-ID: <m1ejmszrpr.fsf@ebiederm.dsl.xmission.com> Date: Tue, 10 Apr 2007 00:08:48 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Johannes Berg <johannes@...solutions.net> Cc: Patrick McHardy <kaber@...sh.net>, greearb@...delatech.com, containers@...ts.osdl.org, shemminger@...ux-foundation.org, kuznet@....inr.ac.ru, dim@...nvz.org, netdev@...r.kernel.org, akpm@...ux-foundation.org, jgarzik@...ox.com, David Miller <davem@...emloft.net> Subject: Re: [PATCH] net: Add etun driver Johannes Berg <johannes@...solutions.net> writes: > Our virtual devices are always associated with a piece of hardware, and > we really want them to be associated with that at all times, even when > not UP. Everything else seems like a huge complication if only because > then we can't have whoever will be responsible for the device allocate > it's private space area. How are you specifying which piece of hardware today? By interface name? What function do your virtual devices serve? I'm trying to wrap my head around the model. 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
Powered by blists - more mailing lists