netdev - Re: [PATCH] Use firmware provided index to register a network interface

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Sep 2010 12:22:28 -0700
From:	Greg KH <greg@...ah.com>
To:	Narendra K <Narendra_K@...l.com>
Cc:	netdev@...r.kernel.org, linux-hotplug@...r.kernel.org,
	linux-pci@...r.kernel.org, matt_domsch@...l.com,
	charles_rose@...l.com, jordan_hargrave@...l.com,
	vijay_nijhawan@...l.com
Subject: Re: [PATCH] Use firmware provided index to register a network
 interface

On Wed, Sep 22, 2010 at 01:31:38PM -0500, Narendra K wrote:
> Hello,
> 
> Here is another approach to address the issue of "eth0 does not always
> map to the Integrated NIC Port 1 as denoted on server chassis label".
> For more details please refer to the thread -
> http://marc.info/?l=linux-netdev&m=128163454631618&w=3.
> 
> Patch makes use of the firmware provided index to derive ethN names.
> That way the naming scheme adheres to the existing requirements of
> ethN namespace and with IFNAMSIZ length.

Ick, again, what's wrong with using udev for this as it is designed to?
That way no kernel changes are needed, and no one has to rely on the
BIOS getting the firmware number right (meaning it will work on all
types of systems.)

thanks,

greg k-h
--
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