All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Mike Anderson <andmike@us.ibm.com>
Subject: Re: Synchronizing scsi_remove_host and the error handler
Date: Mon, 08 Aug 2005 18:20:21 -0400	[thread overview]
Message-ID: <42F7DAA5.7070208@adaptec.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0508081517000.4454-100000@iolanthe.rowland.org>

On 08/08/05 16:41, Alan Stern wrote:
> I still have one related question.  This is a little bit off to one 
> side, but maybe you folks can suggest possible solutions.  The question 
> concerns a deadlock I _was_ able to generate earlier today with a patched
> usb-storage.
> 
> My USB mass-storage test device doesn't respond to TEST UNIT READY, so it
> causes a timeout and kicks the error handler into action.  This happens 
> during device scanning, just prior to reading the partition table.  The 
> error handler goes through various stages of processing, leading up to a 
> bus reset.  I disconnected the USB device just before the bus reset 
> routine was called.

I think that "scanning" is a special process which should involve
the minimum of error handling, by either ignoring errors and trying
to connect to the device anyway, or on the first error, give up
the device.  Which policy would one follow depends on the transport.

If the latter, you need to blacklist the device as not supporting
TUR.  Then on any error, like you pulling the cable during scanning,
the scanning process will give up and all will be well.

	Luben

  parent reply	other threads:[~2005-08-08 22:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 14:59 Synchronizing scsi_remove_host and the error handler Alan Stern
2005-08-07 15:36 ` James Bottomley
2005-08-07 18:43   ` Alan Stern
2005-08-07 21:57     ` James Bottomley
2005-08-08 18:24       ` Luben Tuikov
2005-08-08 19:54         ` Mike Anderson
2005-08-08 20:25           ` Luben Tuikov
2005-08-08 20:06       ` Mike Anderson
2005-08-07 22:15     ` Stefan Richter
2005-08-08 20:41       ` Alan Stern
2005-08-08 21:36         ` Mike Anderson
2005-08-08 22:36           ` Alan Stern
2005-08-08 23:10             ` Stefan Richter
2005-08-09 14:23               ` Alan Stern
2005-08-09 19:37                 ` Stefan Richter
2005-08-09 20:07                   ` Alan Stern
2005-08-09 20:45                     ` Stefan Richter
2005-08-08 23:59             ` Stefan Richter
2005-08-09 14:40               ` Alan Stern
2005-08-09 18:21                 ` Stefan Richter
2005-08-09 18:49                   ` Alan Stern
2005-08-08 21:49         ` Stefan Richter
2005-08-08 22:20         ` Luben Tuikov [this message]
2005-08-08 22:30           ` Alan Stern
2005-08-09  0:49             ` Luben Tuikov
2005-08-09 14:50               ` Alan Stern
2005-08-08 22:23         ` James Bottomley
2005-08-08 22:40           ` Alan Stern
2005-08-08 18:07   ` Luben Tuikov
2005-08-08 18:04 ` Luben Tuikov

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=42F7DAA5.7070208@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stern@rowland.harvard.edu \
    /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.