| 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: <20080419.223241.252348841.davem@davemloft.net> Date: Sat, 19 Apr 2008 22:32:41 -0700 (PDT) From: David Miller <davem@...emloft.net> To: arvidjaar@...l.ru Cc: linux-hotplug@...r.kernel.org, dwmw2@...radead.org, kay.sievers@...y.org, md@...ux.it, harald@...hat.com, netdev@...r.kernel.org, schwidefsky@...ibm.com Subject: Re: [PATCH] Expose netdevice dev_id through sysfs From: Andrey Borzenkov <arvidjaar@...l.ru> Date: Sun, 20 Apr 2008 09:21:03 +0400 > On Sparc system we also have global device tree which provides unique > and persistent reference to every device. Solaris has no problems with > having same MAC for all interfaces. SunOS/Solaris names devices geographically on the I/O bus. So if you move the card from one slot to another, it's a different device and you have to change your configuration, which is pretty bogus. At least under Linux the identity follows the MAC address, which I definitely see as a superior behavior. The only problem is handling the multiple devices with same MAC case. > What is exactly wrong with using device topology path? This should > exist on any system, it is unique and it is persistent. Because if you move the device to a different PCI slot it should still show up as the same device, using the MAC address as the key. The Solaris behavior isn't so intelligent. -- 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