public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Michael Heinz <mheinz@infiniconsys.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Possible bug handling bad I/Os?
Date: Thu, 29 Aug 2002 13:27:28 -0400	[thread overview]
Message-ID: <20020829132728.G31625@redhat.com> (raw)
In-Reply-To: <B993CDEB.2C0F%mheinz@infiniconsys.com>; from mheinz@infiniconsys.com on Thu, Aug 29, 2002 at 01:11:07PM -0400

On Thu, Aug 29, 2002 at 01:11:07PM -0400, Michael Heinz wrote:
> 
> A little more detail - if the caller wasn't checking my return code at all,
> I would expect the SCSI layer to send me an abort when the command times out
> - but it doesn't, it goes inert.

Yep.  It's the queue starvation issue that someone else brought up (can't 
remember who that was...).  Basically, if you don't have some outstanding 
command that will complete after you fail your queue_command() call then 
there is no method of goosing the current holding queue in the mid layer.  
It doesn't have a timer backup goose method as of yet.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2002-08-29 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 13:34 Possible bug handling bad I/Os? Michael Heinz
2002-08-29 16:41 ` Doug Ledford
2002-08-29 16:58   ` Michael Heinz
2002-08-29 17:11   ` Michael Heinz
2002-08-29 17:27     ` Doug Ledford [this message]
2002-08-29 19:16       ` Luben Tuikov
2002-08-29 19:43         ` Doug Ledford
  -- strict thread matches above, loose matches on Subject: below --
2002-08-29 15:12 Martin Peschke3
2002-08-29 15:14 ` Michael Heinz

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=20020829132728.G31625@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mheinz@infiniconsys.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