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]
Date:	Wed, 9 May 2007 10:09:14 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <greg@...ah.com>
cc:	Cornelia Huck <cornelia.huck@...ibm.com>,
	Adrian Bunk <bunk@...sta.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11
 (PCI_MULTITHREAD_PROBE)



On Wed, 9 May 2007, Greg KH wrote:
> 
> Why is it dead?  Since when is PCI the only bus in the system?

Quite frankly, any probing strategy that isn't relevant to PCI simply 
isn't relevant - full stop!

No, it's not the only bus, but if something isn't relevant to PCI it 
shouldn't be in any general bus layer abstraction.  PCI is _that_ dominant 
(and all the modern variations are just extensions on PCI, PCI didn't go 
away just because it's called PCI-X or whatever).

I think buses like SCSI, USB etc are valid things to worry about as being 
very different from PCI, but they are not something that the generic bus 
probing code (as exemplified by the commit in question) should know/care 
about. Whatever probing semantics that a SCSI adapter ends up using for 
probing its bus should be up to the SCSI layer, and there is no point in 
thinking that it should be a "generic bus" abstraction.

In fact, different SCSI adapters would likely have different rules. iSCSI 
probably won't have anything in common with "normal" SCSI when it comes to 
probing, for example.

		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

Powered by Openwall GNU/*/Linux Powered by OpenVZ