Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753094Ab0GISXa (ORCPT ); Fri, 9 Jul 2010 14:23:30 -0400 Received: from exprod6og110.obsmtp.com ([64.18.1.25]:47211 "HELO exprod6og110.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751576Ab0GISX2 convert rfc822-to-8bit (ORCPT ); Fri, 9 Jul 2010 14:23:28 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: nic enumeration Date: Fri, 9 Jul 2010 14:23:26 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: nic enumeration Thread-Index: AcsfibSd0eFrp0D2REqkEuczR1BuaAABBx6A References: <20100708012120.GB11419@auslistsprd01.us.dell.com><82tyo9i0n2.fsf@mid.bfk.de> From: "Loke, Chetan" To: "Steve Fink" Cc: "Florian Weimer" , , "Matt Domsch" , "Michael Di Domenico" , , X-OriginalArrivalTime: 09 Jul 2010 18:23:27.0261 (UTC) FILETIME=[D31B0CD0:01CB1F93] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2110 Lines: 55 > -----Original Message----- > From: Steve Fink [mailto:sphink@gmail.com] > Sent: July 09, 2010 1:11 PM > To: Loke, Chetan > Cc: Florian Weimer; linux-net@vger.kernel.org; Matt Domsch; Michael Di > Domenico; linux-kernel@vger.kernel.org; kay.sievers@vrfy.org > Subject: Re: nic enumeration > > On Fri, Jul 9, 2010 at 9:27 AM, Loke, Chetan > wrote: > > Ok, no renaming, I would like a reference. And symlink just doesn't > work > > w/ the udevadm trigger business. We've tried that already. > > > > What needs to be changed in udev etc to create a soft link? Any place > > where I should start digging and gotchas to lookout for? > > By "soft link", I assume you're talking figuratively? Yes, I was using it loosely. symlink == I would like 'udev' to do the linkage w/ the network-devices and create a reference to it. > Soft (symbolic) > links are a filesystem concept, implemented by filesystem-specific > logic that knows how to read a filename out of an inode and restart > lookup. In order for something similar to work for network devices, > somebody would have had to explicitly implement similar functionality. > (Symlinks are a big headache and source of security holes -- access > control, loops, pointing to nonexistent files, etc. -- so there's a > good reason to NOT have an equivalent for network devices.) > Huh? If the 'ethX' interface doesn't exist just don't create the 'link'. So are you saying there are no security issues with udev-symlinks for other subsystems? Why is renaming allowed on the network-interface then? Isn't that a problem? I don't see the driver re-registering their RX/TX queues with the new-if-name. May be I'm overlooking at something really obvious. But how are people managing [pv]drivers with multiple vNICs in their VMs if they need a consistent naming scheme? Regards Chetan Loke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/