Hi, On Thu, Jun 19, 2008 at 11:39 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 19 Jun 2008, Matthew Wilcox wrote: > >> This discussion seemed to die off ... did anything ever come of it? > > As I recall, it died because the whole notion was very poorly defined > to begin with. The idea was to stop waiting when all the SCSI buses > had been scanned -- but there's no way to know when that occurs because > new buses can be added at any time. Can you please explain why this is? We only want to scan buses that are present when the system is started. If we reach the point where all USB ports/devices/whatever have been enumerated, all SCSI buses scanned, and all partition tables loaded, what more is there to wait for? I can't understand that this is fundamentally a hardware problem. I understand that there might be a problem with the patch that was proposed a the beginning of the thread, but is this really a truly unsolvable problem? Please correct me if I am wrong -- the problem here is that Pekka's newly introduced nr_root_scans can drop to 0 before everything has been enumerated at least once. This is because scsi_scan_host() forks a new thread which is what's actually doing the scanning. Can't we just stick a begin_root_scan() before forking, and drop it inside the thread, just like we do with the usb_stor_scan_thread? If the thread is actually a loop, the first iteration should be enough, right? I'm grateful for any explanations that will help my poor head understand... :-) Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
