| 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: Wed, 9 May 2007 10:25:57 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Greg KH <greg@...ah.com> cc: david@...g.hm, Cornelia Huck <cornelia.huck@...ibm.com>, Adrian Bunk <bunk@...sta.de>, linux-kernel <linux-kernel@...r.kernel.org>, Duncan Sands <duncan.sands@...h.u-psud.fr> Subject: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE) On Wed, 9 May 2007, Greg KH wrote: > > > > but then won't the devices get registered in a random order? (i.e. whenever > > the async portion finishes the probing and finds the details of what there > > is to register) > > So? We have busses today that have devices get registered in random > order, our userspace tools can handle it just fine now. However, that does *not* translate to: "..so we can do it for all buses". People *do* depend on simple things like internal harddisks showing up in a particular order. The fact that you *can* handle it with UUID's etc does not mean that people do, or that they should be forced to do so. There is no inherent goodness in making the bootup more random. In fact, there's a lot of badness to it, ranging from just not being very nice to "really a bitch to debug". And no amount of "user level _could_ handle it" changes that. Linus - 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