linux-kernel - PCI probe order changes after 2.6.22

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20080411185530.GA20746@linuxace.com>
Date:	Fri, 11 Apr 2008 11:55:30 -0700
From:	Phil Oester <kernel@...uxace.com>
To:	linux-kernel@...r.kernel.org
Subject: PCI probe order changes after 2.6.22

In commit 08f1c192c3c32797068bfe97738babb3295bbf42 (x86-64: introduce
struct pci_sysdata to facilitate sharing of ->sysdata), a change was
made from using pcibios_scan_root to pci_scan_bus_parented.  pcibios_scan_root
applies some quirks to various systems via pciprobe_dmi_table, including a
number of Dell PowerEdge servers.  The similarly named acpi_pciprobe_dmi_table,
however, does not apply the same set_bf_sort quirk, so between .22 and .23, the
onboard Broadcom nics reversed their probe order.

Any chance this can get fixed?  The brainless fix would be to duplicate all
the pciprobe_dmi_table fixups in acpi_pciprobe_dmi_table, but perhaps there
is a better approach which could reuse the code?

Thanks,
Phil
--
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/