From: Subhash Jadavani <subhashj@codeaurora.org>
To: Zang Leigang <zangleigang@hisilicon.com>
Cc: vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-scsi-owner@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: remove unnecessary UFSHCD_STATE_ERROR set
Date: Tue, 15 Nov 2016 11:00:12 -0800 [thread overview]
Message-ID: <fb242d9166cda04eaebf53d776915f60@codeaurora.org> (raw)
In-Reply-To: <20161115122533.75266-1-zangleigang@hisilicon.com>
On 2016-11-15 04:25, Zang Leigang wrote:
> We set ufshcd_state to UFSHCD_STATE_ERROR when an err handler
> fails. So I think UFSHCD_STATE_ERROR means host not works any more.
> Set it before schedule eh_work is not correct.
>
> Signed-off-by: Zang Leigang <zangleigang@hisilicon.com>
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index 05c7456..a7724ad 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -4158,7 +4158,6 @@ static void ufshcd_check_errors(struct ufs_hba
> *hba)
> /* block commands from scsi mid-layer */
> scsi_block_requests(hba->host);
>
> - hba->ufshcd_state = UFSHCD_STATE_ERROR;
But we may still want to stop the new requests from being issued (via
ufshcd_queuecommand) until error handler (ufshcd_err_handler()) gets
chance to run. May be a new intermediate state like
UFSHCD_STATE_EH_SCHEDULED should be added and set here, we have to check
the same in ufshcd_queuecommand() to return busy if ufshcd_state is
UFSHCD_STATE_EH_SCHEDULED.
> schedule_work(&hba->eh_work);
> }
> }
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-15 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 12:25 [PATCH] scsi: ufs: remove unnecessary UFSHCD_STATE_ERROR set Zang Leigang
2016-11-15 19:00 ` Subhash Jadavani [this message]
2016-11-16 3:13 ` Zang Leigang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb242d9166cda04eaebf53d776915f60@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vinholikatti@gmail.com \
--cc=zangleigang@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).