public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: martin@lorenz.eu.org,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-usb-devel] usb-storage / scsi : new scsi host on each plug
Date: 29 Oct 2003 09:53:33 -0600	[thread overview]
Message-ID: <1067442814.1829.21.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0310291020430.874-100000@ida.rowland.org>

On Wed, 2003-10-29 at 09:24, Alan Stern wrote:
> > no matter which USB-storage-device I attach (tried CD-ROM, 
> > Flash Card Reader and memory stick) I get a new scsi host
> > every time i plug a device in.
> > 
> > so when changing devices for several times I finally end up
> > with /dev/scsi/host0 to 17 or more (diden't go on)
>
> This is a SCSI issue, not a USB one.  Maybe someone on the 
> SCSI development list can enlighten us.  As far as I can tell, the host 
> number is simply incremented every time a new host, of whatever sort, is 
> added.  The numbers never get reused.

This is really a design feature.  Not reusing hosts gives us time to
clean up the old one before the new one is initialised (and prevents
races where we could be trying to plug in a new host at the same time
we're cleaning up the old one).

In 2.6 udev discovery should ensure these devices come back to the same
name.

James



  reply	other threads:[~2003-10-29 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AEoQX-0005kQ-Cz@mail.holoclan.de>
2003-10-29 15:24 ` [linux-usb-devel] usb-storage / scsi : new scsi host on each plug Alan Stern
2003-10-29 15:53   ` James Bottomley [this message]
2003-11-07  6:24     ` Douglas Gilbert

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=1067442814.1829.21.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=martin@lorenz.eu.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox