From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: jiang.biao2@zte.com.cn
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Patch] scsi_error: should not get sense for timeout IO in scsi error handler
Date: Wed, 26 Aug 2015 17:31:29 -0700 [thread overview]
Message-ID: <1440635489.2196.98.camel@HansenPartnership.com> (raw)
In-Reply-To: <OFAF74C95C.6058723F-ON48257E93.00322982-48257E93.00363C6C@zte.com.cn>
On Fri, 2015-07-31 at 17:52 +0800, jiang.biao2@zte.com.cn wrote:
> scsi_error: should not get sense for timeout IO in scsi error handler
>
> When an IO timeout occurs, the IO will be aborted in
> scsi_abort_command() and SCSI_EH_ABORT_SCHEDULED will be set. Because
> of that, the SCSI_EH_CANCEL_CMD will be clear in scsi_eh_scmd_add().
> So when scsi error handler starts, it will get sense for this
> timeout IO and the scmd of the IO request will be reused. In that
> case, the scmd may be double released when racing with io_done(),
> which will result in crash.
> SO SCSI_EH_ABORT_SCHEDULED should also be checked when getting sense.
> The bug maybe reproduced when the link between host and disk is
> unstable.
>
> Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn>
> Signed-off-by: Long Chun <long.chun@zte.com.cn>
> Reviewed-by: Tan Hu <tan.hu@zte.com.cn>
> Reviewed-by: Chen Donghai <chen.donghai@zte.com.cn>
> Reviewed-by: Cai Qu <cai.qu@zte.com.cn>
>
> diff -uprN drivers/scsi/scsi_error.c drivers_new/scsi/scsi_error.c
to apply easily, diffs need to start at the top of the tree, please.
> --- scsi/scsi_error.c 2015-07-31 16:03:18.000000000 +0800
> +++ scsi_new/scsi_error.c 2015-07-31 16:29:25.000000000 +0800
> @@ -1156,9 +1156,14 @@ int scsi_eh_get_sense(struct list_head *
> struct Scsi_Host *shost;
> int rtn;
>
> + /*
> + * If SCSI_EH_ABORT_SCHEDULED has been set, it is timeout IO,
> + * should not get sense.
> + */
> list_for_each_entry_safe(scmd, next, work_q, eh_entry) {
and here all the tabs have been converted to spaces; you need to read
Documentation/email-clients.txt for details on how to avoid this.
I managed to fix it up this time, but won't again.
James
prev parent reply other threads:[~2015-08-27 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 9:52 [Patch] scsi_error: should not get sense for timeout IO in scsi error handler jiang.biao2
2015-07-31 13:17 ` Hannes Reinecke
2015-08-01 4:39 ` 答复: " jiang.biao2
[not found] ` <OF7187F435.4453DB49-ON48257E94.000CC72C-48257E94.000D6550@zte.com.cn>
2015-08-01 7:37 ` Hannes Reinecke
2015-08-27 0:31 ` James Bottomley [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=1440635489.2196.98.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jiang.biao2@zte.com.cn \
--cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).