From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Mid-layer handling of NOT_READY conditions...
Date: Sat, 29 Jan 2005 10:44:41 -0600 [thread overview]
Message-ID: <1107017081.4535.29.camel@mulgrave> (raw)
In-Reply-To: <1106977566.9862.102.camel@plap>
On Fri, 2005-01-28 at 21:46 -0800, Andrew Vasquez wrote:
> Returning back DID_IMM_RETRY for these 'transport' related conditions
> would of course help in this issue -- but at the same time bring with it
> several side-effects which may not be desirable.
>
> So, beyond this particular circumstance, what would be considered a
> 'proper' return status for this type of event?
Well, the correct return, since this is a condition from the storage, is
simply the check condition and the sense code (rather than having the
driver interpret it).
> > Would this be an approach to consider? Or should we tackle the problem
> > by addressing the quirky (cmd->retries > cmd->allowed) state?
That's what I think the correct approach should be....we have a few
other quirky devices that aren't pleased with our current NOT_READY
handling. Were you going to look into coding up a patch for this?
James
next prev parent reply other threads:[~2005-01-29 16:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 23:24 Mid-layer handling of NOT_READY conditions Andrew Vasquez
2005-01-29 5:46 ` Andrew Vasquez
2005-01-29 16:16 ` Matthew Wilcox
2005-01-29 16:44 ` James Bottomley [this message]
2005-01-29 19:34 ` Patrick Mansfield
2005-01-30 1:40 ` James Bottomley
2005-01-30 2:33 ` Douglas Gilbert
2005-01-31 7:47 ` Andrew Vasquez
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 9:46 Mid-Layer handling of NOT READY conditions EXT / DEVOTEAM VAROQUI Christophe
2005-01-31 14:07 goggin, edward
2005-01-31 16:56 Mid-layer handling of NOT_READY conditions James.Smart
2005-01-31 17:36 ` Patrick Mansfield
2005-02-01 7:21 ` Andrew Vasquez
2005-01-31 18:22 ` Andrew Vasquez
2005-01-31 19:07 James.Smart
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=1107017081.4535.29.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andrew.vasquez@qlogic.com \
--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