netdev - Re: bnx2 probe order change from 2.6.21 -> 2.6.24

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: <1207854953.5248.2.camel@dell>
Date:	Thu, 10 Apr 2008 12:15:50 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Phil Oester" <kernel@...uxace.com>
cc:	netdev <netdev@...r.kernel.org>
Subject: Re: bnx2 probe order change from 2.6.21 -> 2.6.24

On Thu, 2008-04-10 at 10:54 -0700, Phil Oester wrote:
> On Thu, Apr 10, 2008 at 11:45:16AM -0700, Michael Chan wrote:
> > I know there is a difference in PCI probing order between 2.4 and 2.6
> > kernels on x86 machines, but I'm not aware of changes in these 2 recent
> > 2.6 kernels you mentioned above.  Various kernel parameters such as
> > pci=nosort, pci=bfsort, pci=nobfsort can affect the order.  Are you
> > using any of these?
> 
> No - nothing like that.  And the e1000 devices in the box (eth0 - 7) are probing
> in the same order, which (perhaps incorrectly) leads me to believe it's not
> PCI related, but specific to bnx2.
> 

The driver has no control over the ordering of these devices.  The PCI
layer scans the buses in the order it chooses and calls the driver's
probe method for every matching device that it finds.

--
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