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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Apr 2007 11:52:02 +0200 From: Patrick McHardy <kaber@...sh.net> To: Johannes Berg <johannes@...solutions.net> CC: "Eric W. Biederman" <ebiederm@...ssion.com>, David Miller <davem@...emloft.net>, akpm@...ux-foundation.org, dim@...nvz.org, netdev@...r.kernel.org, jgarzik@...ox.com, containers@...ts.osdl.org, kuznet@....inr.ac.ru, shemminger@...ux-foundation.org, greearb@...delatech.com Subject: Re: [PATCH] net: Add etun driver Johannes Berg wrote: > On Tue, 2007-04-10 at 09:52 +0200, Patrick McHardy wrote: > > >>Shouldn't be a problem either. Creating the device atomically also >>prevents that anything else is setting them UP before they're fully >>configured. > > > How would you do it generically then? I'm absolutely not opposed to the > idea but for now haven't seen how to do it. Without having thought much about it yet, roughly like this: - driver receives RTM_NEWLINK message (under rtnl) - driver allocates new device - driver initializes device based on content of RTM_NEWLINK message - driver returns Device creation won't be generic of course since only the driver knows how to do that. - 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