summaryrefslogtreecommitdiff
path: root/drivers/mmc/core
diff options
context:
space:
mode:
authorAdrian Hunter <adrian.hunter@nokia.com>2010-01-08 14:43:00 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2010-01-11 09:34:06 -0800
commit5fa83ce284a4b7cd9dcfadd01500b0ed4ab9b740 (patch)
tree853c2e06c085fba633bcfef2c624a068adf2bbf5 /drivers/mmc/core
parent0a74ff29b8dd8b748f8856352f9a9b5c6cc362cc (diff)
downloadlwn-5fa83ce284a4b7cd9dcfadd01500b0ed4ab9b740.tar.gz
lwn-5fa83ce284a4b7cd9dcfadd01500b0ed4ab9b740.zip
mmc_block: fix queue cleanup
The main bug was that 'blk_cleanup_queue()' was called while the block device could still be in use, for example, because the card was removed while files were still open. In addition, to be sure that 'mmc_request()' will get called for all new requests (so it can error them out), the queue is emptied during cleanup. This is done after the worker thread is stopped to avoid racing with it. Finally, it is not a device error for this to be happening, so quiet the (sometimes very many) error messages. Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com> Cc: <linux-mmc@vger.kernel.org> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/mmc/core')
0 files changed, 0 insertions, 0 deletions