From: Doug Ledford <dledford@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] 2.4 SCSI error handling fixes
Date: Thu, 12 Sep 2002 14:18:06 -0400 [thread overview]
Message-ID: <20020912141806.J1551@redhat.com> (raw)
In-Reply-To: <20020912191354.B4739@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Sep 12, 2002 at 07:13:54PM +0100
On Thu, Sep 12, 2002 at 07:13:54PM +0100, Russell King wrote:
> - scsi_setup_cmd_retry(SCpnt);
> - scsi_send_eh_cmnd(SCpnt, SCpnt->timeout_per_command);
> + do {
> + scsi_setup_cmd_retry(SCpnt);
> + scsi_send_eh_cmnd(SCpnt, SCpnt->timeout_per_command);
> + } while (SCpnt->eh_state == NEEDS_RETRY);
> + * If the SCSI device responded with "logical unit
> + * is in process of becoming ready", we need to
> + * retry this command.
> + */
> + } while (SCpnt->eh_state == NEEDS_RETRY);
> + /*
> + * If the SCSI device responded with "logical unit
> + * is in process of becoming ready", we need to
> + * retry this command.
> + */
> + } while (SCpnt->eh_state == NEEDS_RETRY);
> default:
> - SCpnt->eh_state = FAILED;
> + ret = FAILED;
> + /*FALLTHROUGH*/
> + case FAILED:
> + case NEEDS_RETRY:
> + case SUCCESS:
> + SCpnt->eh_state = ret;
> break;
> }
> } else {
I don't see any bounding here. You *have* to bound this. It is not that
uncommon for a device to report "logical unit is in the process of
becoming ready" forever on certain types of hardware failures. Without
bounding, we won't ever give up on it.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-09-12 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 18:13 [PATCH 2/4] 2.4 SCSI error handling fixes Russell King
2002-09-12 18:18 ` Doug Ledford [this message]
2002-09-12 18:20 ` Russell King
2002-09-12 19:31 ` Mike Anderson
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=20020912141806.J1551@redhat.com \
--to=dledford@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.