Return-Path: Received: from mga02.intel.com ([134.134.136.20]:41695 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754703AbdC1LKD (ORCPT ); Tue, 28 Mar 2017 07:10:03 -0400 From: Adrian Hunter To: stable@vger.kernel.org Cc: gregkh@linuxfoundation.org, Ulf Hansson Subject: [PATCH v4.10] mmc: block: Fix is_waiting_last_req set incorrectly Date: Tue, 28 Mar 2017 14:04:27 +0300 Message-Id: <1490699067-9499-1-git-send-email-adrian.hunter@intel.com> Sender: stable-owner@vger.kernel.org List-ID: commit 2602b740e45cc64feb55d5a9ee8db744ab3becbb upstream. Commit 15520111500c ("mmc: core: Further fix thread wake-up") allowed a queue to release the host with is_waiting_last_req set to true. A queue waiting to claim the host will not reset it, which can result in the queue getting stuck in a loop. Fixes: 15520111500c ("mmc: core: Further fix thread wake-up") Signed-off-by: Adrian Hunter Signed-off-by: Ulf Hansson --- drivers/mmc/core/block.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c index cb1698f268f1..7f4927a05be0 100644 --- a/drivers/mmc/core/block.c +++ b/drivers/mmc/core/block.c @@ -1791,6 +1791,7 @@ int mmc_blk_issue_rq(struct mmc_queue *mq, struct request *req) ret = mmc_blk_issue_flush(mq, req); } else { ret = mmc_blk_issue_rw_rq(mq, req); + card->host->context_info.is_waiting_last_req = false; } out: -- 1.9.1