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]

Message-ID: <b263e5900609142053r12fbb71ep6ea3e1d63a722d4e@mail.gmail.com>
Date:	Thu, 14 Sep 2006 20:53:16 -0700
From:	"Dan Carpenter" <error27.lkml@...il.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, error27@...il.com,
	ppokorny@...guincomputing.com
Subject: Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first

On 9/7/06, Matt Domsch <Matt_Domsch@...l.com> wrote:
> Problem:
> 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.
>

On RHEL3 the 32bit and 64bit versions order the NICs differently.
64bit RHEL3 orders it the same as 2.6.

I've got a lot of systems where the NIC LEDs are labelled.  The labels
are correct for 2.6 but not for 2.4 32 bit.  I'm suspect the labels
were designed for Windows originally.

My boss pointed out that this patch.  It was supposed to make PCI bus
ordering match 2.4.
http://kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=ffdd6e8f870ca6dd0d9b9169b8c2e0fdbae99549
It's still there, why did it stop working?

Couldn't we just use the labelling from the DMI data to order the NICs?

regards,
dan carpenter
-
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/