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: set host_byte to DID_REQUEUE when ocs = OCS_ABORTED
Date: Wed, 28 Jun 2017 16:42:36 -0700 [thread overview]
Message-ID: <7bb81ce8005715d416539754246b2989@codeaurora.org> (raw)
In-Reply-To: <20170624102722.4050-1-zangleigang@hisilicon.com>
On 2017-06-24 03:27, Zang Leigang wrote:
> Host set ocs to OCS_ABORTED when clear a doorbell in err handler.
OCS field is valid after host controller has cleared the corresponding
doorbell (UTRLDBR) bit to zero. And here HW would be clearing the
doorbell bit, not the SW. So I am not sure what do you mean in sentence
above? Can you please elaborate more on this?
> Then scsi_decide_disposition return SUCCESS. This may cause some
> filesystem panic because a FAILED REQUESET. Requeue and complete is
> better.
Why do you think retrying this HW aborted request will succeed next
time? Are we going to fix some request parameters before retrying? If
not, it will most likely fail again.
>
> Signed-off-by: Zang Leigang <zangleigang@hisilicon.com>
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index ffe8d8608818..e050dcea1bea 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -4545,8 +4545,6 @@ ufshcd_transfer_rsp_status(struct ufs_hba *hba,
> struct ufshcd_lrb *lrbp)
> }
> break;
> case OCS_ABORTED:
> - result |= DID_ABORT << 16;
> - break;
> case OCS_INVALID_COMMAND_STATUS:
> result |= DID_REQUEUE << 16;
> break;
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-28 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 10:27 [PATCH] scsi: ufs: set host_byte to DID_REQUEUE when ocs = OCS_ABORTED Zang Leigang
2017-06-28 1:34 ` Martin K. Petersen
2017-06-28 23:42 ` Subhash Jadavani [this message]
2017-06-29 2:25 ` Zang Leigang
2017-07-03 21:28 ` Subhash Jadavani
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=7bb81ce8005715d416539754246b2989@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.