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: Tue, 8 May 2007 08:15:22 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Cornelia Huck <cornelia.huck@...ibm.com> cc: Greg K-H <greg@...ah.com>, Adrian Bunk <bunk@...sta.de>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE) On Tue, 8 May 2007, Cornelia Huck wrote: > > As I wanted to add multithreaded probing for some s390 busses, I > discovered that the commit above removed the multithreaded probing > infrastructure again, while just some days before some of my patches > reworking it had been merged... No. I am *not* reverting that patch. The whole PCI bus-level multi-threaded stuff was an incredibly broken idea. If you have problems with probing, it's not going to be about the host bus. It might be things like SCSI buses etc, and if somebody makes *those* be more threaded, I'm ok with it. But I'm not going to accept another broken PCI bus probe threading patch. > (OK, PCI_MULTITHREAD_PROBE should not depend on BROKEN, but on > EXPERIMENTAL with the reworked probing infrastructure. This got mixed > up, I can send a patch that changes it.) No. No. No. Probing the core bus was broken. Not "experimental". Broken. It not only threaded the wrogn area entirely, it also totally screwed up several driver subsystems (like IDE). 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