Alex Dubov wrote:
>
> You'll agree, I think, that add_disk in mmc_block_probe issues a lot of
> requests (reads partition
> table, fs superblocks and such - plenty of room for critical errors). Then,
> driver's remove method
> will not be called before driver's probe method had finished. So mmc_block is
> quite involved, even
> though it does not affect the problem's resolution.
I agree that mmc_block's probe method will generate a whole bunch of requests.
But I don't see how that can be called given the scenario you describe.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
