diff options
author | Arjan van de Ven <arjan@linux.intel.com> | 2009-04-21 20:32:54 (GMT) |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-22 02:40:00 (GMT) |
commit | d4d5291c8cd499b1b590336059d5cc3e24c1ced6 (patch) | |
tree | bb4c2ea559001e066bf3355c1e4d82b36cb916d6 /arch/arm | |
parent | 5dd559f020c98a2a4b3e063f09c0e4bc771ed838 (diff) | |
download | linux-fsl-qoriq-d4d5291c8cd499b1b590336059d5cc3e24c1ced6.tar.xz |
driver synchronization: make scsi_wait_scan more advanced
There is currently only one way for userspace to say "wait for my storage
device to get ready for the modules I just loaded": to load the
scsi_wait_scan module. Expectations of userspace are that once this
module is loaded, all the (storage) devices for which the drivers
were loaded before the module load are present.
Now, there are some issues with the implementation, and the async
stuff got caught in the middle of this: The existing code only
waits for the scsy async probing to finish, but it did not take
into account at all that probing might not have begun yet.
(Russell ran into this problem on his computer and the fix works for him)
This patch fixes this more thoroughly than the previous "fix", which
had some bad side effects (namely, for kernel code that wanted to wait for
the scsi scan it would also do an async sync, which would deadlock if you did
it from async context already.. there's a report about that on lkml):
The patch makes the module first wait for all device driver probes, and then it
will wait for the scsi parallel scan to finish.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Tested-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions