From: Douglas Gilbert <dougg@torque.net>
To: SCSI development list <linux-scsi@vger.kernel.org>
Cc: Saeed.Bishara@il.marvell.com, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH] lk 2.4.27 error handling, ad infinitum
Date: Fri, 03 Sep 2004 10:06:17 +1000 [thread overview]
Message-ID: <4137B579.1050806@torque.net> (raw)
In-Reply-To: <4136EE87.2080409@torque.net>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Douglas Gilbert wrote:
> dougg wrote:
> > The following scenario has been brought to my attention.
> >
> > While handling a error (e.g. a timeout) the
> > scsi_send_eh_cmnd() function issues a (stalled) queued command.
> > Now that command hits a repeatable failure (e.g. MEDIUM ERROR).
> >
> > In this scaenario it would seem that the "goto retry" forms
> > an infinite loop re-issuing that command on the same (broken)
> > block.
> >
> > Comments?
>
> No comments, so how about this patch. When the eh retries are
> exhausted the code drops through to FAILED state. If a command
> in foreground (i.e. not sent by the eh handler) exceeds it retries
> then SUCCESS is returned??
Saeed reports that breaking out of the retry loop with
eh_state set to SUCCESS does successfully handle the
problem.
Change:
- break out of a repeatable error retries when already
in "eh" (error handling) mode
Doug Gilbert
[-- Attachment #2: scsi_error2427_retry2.diff --]
[-- Type: text/x-patch, Size: 416 bytes --]
--- linux/drivers/scsi/scsi_error.c 2004-04-17 19:30:54.000000000 +1000
+++ linux/drivers/scsi/scsi_error.c2427retry2 2004-09-03 09:47:27.174358136 +1000
@@ -664,7 +664,10 @@
SCpnt->eh_state = SUCCESS;
break;
case NEEDS_RETRY:
- goto retry;
+ if ((++SCpnt->retries) < SCpnt->allowed)
+ goto retry;
+ SCpnt->eh_state = SUCCESS;
+ break;
case FAILED:
default:
SCpnt->eh_state = FAILED;
prev parent reply other threads:[~2004-09-03 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 9:57 [PATCH] lk 2.4.27 error handling, ad infinitum Douglas Gilbert
2004-09-02 11:44 ` Saeed Bishara
2004-09-03 0:06 ` Douglas Gilbert [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=4137B579.1050806@torque.net \
--to=dougg@torque.net \
--cc=Saeed.Bishara@il.marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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