From: Wei Fang <fangwei1@huawei.com>
To: <tj@kernel.org>, <jejb@linux.vnet.ibm.com>,
<martin.petersen@oracle.com>, <corbet@lwn.net>
Cc: <hch@infradead.org>, <dan.j.williams@intel.com>,
<linux-ide@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] scsi: fix race between simultaneous decrements of ->host_failed
Date: Thu, 2 Jun 2016 16:33:21 +0800 [thread overview]
Message-ID: <574FEF51.8090907@huawei.com> (raw)
In-Reply-To: <1464854088-26360-1-git-send-email-fangwei1@huawei.com>
Forgot to add changes, please ignore it.
On 2016/6/2 15:54, Wei Fang wrote:
> sas_ata_strategy_handler() adds the works of the ata error handler
> to system_unbound_wq. This workqueue asynchronously runs work items,
> so the ata error handler will be performed concurrently on different
> CPUs. In this case, ->host_failed will be decreased simultaneously in
> scsi_eh_finish_cmd() on different CPUs, and become abnormal.
>
> It will lead to permanently inequal between ->host_failed and
> ->host_busy, and scsi error handler thread won't become running.
> IO errors after that won't be handled forever.
>
> Since all scmds must have been handled in the strategy handle, just
> remove the decrement in scsi_eh_finish_cmd() and zero ->host_busy
> after the strategy handle to fix this race.
>
> This fixes the problem introduced in
> commit 50824d6c5657 ("[SCSI] libsas: async ata-eh").
>
> Signed-off-by: Wei Fang <fangwei1@huawei.com>
> ---
> drivers/ata/libata-eh.c | 2 +-
> drivers/scsi/scsi_error.c | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> index 961acc7..91a9e6a 100644
> --- a/drivers/ata/libata-eh.c
> +++ b/drivers/ata/libata-eh.c
> @@ -606,7 +606,7 @@ void ata_scsi_error(struct Scsi_Host *host)
> ata_scsi_port_error_handler(host, ap);
>
> /* finish or retry handled scmd's and clean up */
> - WARN_ON(host->host_failed || !list_empty(&eh_work_q));
> + WARN_ON(!list_empty(&eh_work_q));
>
> DPRINTK("EXIT\n");
> }
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index 984ddcb..1b9c049 100644
> --- a/drivers/scsi/scsi_error.c
> +++ b/drivers/scsi/scsi_error.c
> @@ -1127,7 +1127,6 @@ static int scsi_eh_action(struct scsi_cmnd *scmd, int rtn)
> */
> void scsi_eh_finish_cmd(struct scsi_cmnd *scmd, struct list_head *done_q)
> {
> - scmd->device->host->host_failed--;
> scmd->eh_eflags = 0;
> list_move_tail(&scmd->eh_entry, done_q);
> }
> @@ -2226,6 +2225,9 @@ int scsi_error_handler(void *data)
> else
> scsi_unjam_host(shost);
>
> + /* All scmds have been handled */
> + shost->host_failed = 0;
> +
> /*
> * Note - if the above fails completely, the action is to take
> * individual devices offline and flush the queue of any
>
prev parent reply other threads:[~2016-06-02 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:54 [PATCH 1/2] scsi: fix race between simultaneous decrements of ->host_failed Wei Fang
2016-06-02 7:54 ` [PATCH 2/2] Documentation/scsi: update scsi_eh.txt about ->host_failed Wei Fang
2016-06-02 8:33 ` Wei Fang [this message]
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=574FEF51.8090907@huawei.com \
--to=fangwei1@huawei.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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