mmc: core: Fix deadlock when the CONFIG_MMC_UNSAFE_RESUME is not defined
authorSujit Reddy Thumma <sthumma@codeaurora.org>
Wed, 23 Nov 2011 03:13:18 +0000 (08:13 +0530)
committerChris Ball <cjb@laptop.org>
Sat, 10 Dec 2011 21:18:39 +0000 (16:18 -0500)
commit49df78074963c97e25debc3c67b72f059111607d
tree8e5e8779f9c3228b5a04044bc077b78eac456fc2
parent524bfca2b42a7c9dc43af13e1592b21dd1ce3fcc
mmc: core: Fix deadlock when the CONFIG_MMC_UNSAFE_RESUME is not defined

mmc_suspend_host() tries to claim host during suspend
and release it only when the bus suspend operation is
compeleted. If CONFIG_MMC_UNSAFE_RESUME is defined and
the host is flagged as removable, mmc_suspend_host()
tries to remove the card. In this process, the file system
sync can get blocked trying to acquire host which is already
claimed by mmc_suspend_host() causing deadlock.

Fix this deadlock by releasing host before ->remove() is called.

Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
Acked-by: Ulf Hansson <ulf.hansson@stericsson.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
drivers/mmc/core/core.c