| 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
| ||
|
Date: Sat, 9 Sep 2006 16:37:44 +0200 From: Ragnar Kjørstad <kernel@...nark.vestdata.no> To: Matt Domsch <Matt_Domsch@...l.com> Cc: linux-kernel@...r.kernel.org Subject: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first [ I'm not subscribed. Please CC me on replies ] > Solution: > > The solution can come in multiple steps. > > Suggested fix #1: kernel > Patch below sorts the two device lists into breadth-first ordering to > maintain compatibility with 2.4 kernels. It also overloads the > 'pci=nosort' option to disable the breadth-first sort (and on i386 it > continues to disable the pcibios_find_device sort as well). As far as I understand it's difficult to argue that sorting the devices one way is more "correct" than the other, so your argument is basically: 1) Compability with 2.4 2) Consistency with BIOS and external labels. Both are important, but the problem is 1) Compability with 2.4 means breaking compability with previous 2.6 kernels. And 2.6 has been out long enough that it's more important than 2.4. 2) There is also hardware where the 2.6 behaviour is consistent with BIOS and external labels where 2.4 is not. An _option_ to enable 2.4 compatible device ordering on the other hand would have just advantages, no disadvantages. -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com Scaling the Linux Datacenter - 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/
Powered by blists - more mailing lists