linux-kernel - Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first

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:	Fri, 8 Sep 2006 11:56:39 -0400
From:	Dave Jones <davej@...hat.com>
To:	Matt Domsch <Matt_Domsch@...l.com>
Cc:	linux-pci@...ey.karlin.mff.cuni.cz, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first

On Thu, Sep 07, 2006 at 10:14:22PM -0500, Matt Domsch wrote:
 > Problem:
 > New Dell PowerEdge servers have 2 embedded ethernet ports, which are
 > labeled NIC1 and NIC2 on the chassis, in the BIOS setup screens, and
 > in the printed documentation.  Assuming no other add-in ethernet ports
 > in the system, Linux 2.4 kernels name these eth0 and eth1
 > respectively.  Many people have come to expect this naming.  Linux 2.6
 > kernels name these eth1 and eth0 respectively (backwards from
 > expectations).  I also have reports that various Sun and HP servers
 > have similar behavior.
 
This came up years back when 2.6 was something new, and the answer
then was 'bind the interface to the MAC address'.

Whilst your patch will fix the case that's currently broken (2.4->2.6),
doesn't it offer equal possibility to break existing setups when people move
from <=2.6.18 -> 2.6.19 ?

	Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/