public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Tim Pepper <tpepper@vato.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Mike Anderson <andmike@us.ibm.com>, Jens Axboe <axboe@suse.de>,
	olh@suse.de
Subject: Re: Bad reactions to QUEUE FULL
Date: 30 Apr 2003 09:58:31 -0500	[thread overview]
Message-ID: <1051714713.1818.32.camel@mulgrave> (raw)
In-Reply-To: <20030429220259.A13386@jose.vato.org>

On Wed, 2003-04-30 at 00:02, Tim Pepper wrote:
> Anybody interested in having a look at this or is it a known issue?

Actually, I'd be most interested in knowing what the problem is that the
patch solves.

The "old" fields (and all inconsistently named) are designed to keep a
copy of the original command for when the actual command gets re-used. 
This re-use happens in the error handler (to get sense, send TURs etc)
and sometimes in the device drivers if they simulate ACA).  Everything
that replaces the command is supposed to copy the old one back after
it's finished using it.

However, QUEUE FULL is a status return, not a sense code, so any command
that gets QUEUE FULL should be an original command, and thus not need
the fields replacing.  Even more curious, if the command were replaced,
then more fields than just the data direction would need putting back.

A viable theory seems to be that the drivers (qlogic and emulex) change
the sc_data_direction field for their own purposes and forget to restore
it again.  I don't have the source, so I can't check this.

Does anyone have any other theories?

James



  reply	other threads:[~2003-04-30 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30  5:02 Bad reactions to QUEUE FULL Tim Pepper
2003-04-30 14:58 ` James Bottomley [this message]
2003-04-30 16:08   ` Mike Anderson
2003-04-30 16:13     ` Tim Pepper
2003-04-30 16:51       ` Mike Anderson
2003-05-05  4:09         ` Tim Pepper

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=1051714713.1818.32.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andmike@us.ibm.com \
    --cc=axboe@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=tpepper@vato.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