public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Ben Collins <bcollins@debian.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: FWD: [BK PATCH] SCSI host num allocation improvement
Date: Fri, 27 Feb 2004 08:56:22 +0100	[thread overview]
Message-ID: <1077868581.4443.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040227010411.GB819@phunnypharm.org>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Fri, 2004-02-27 at 02:04, Ben Collins wrote:
> On Thu, Feb 26, 2004 at 04:56:01PM -0800, Matthew Dharm wrote:
> > My only concern with something like this is the userspace race problem.
> > i.e the following sequence of events:
> > 
> > (1) User uses cdrecord -scanbus to locate their device (host:bus:dev:lun)
> > (2) HBA is disconnected 
> > (3) New HBA is added
> > (4) User issues command to host:bus:dev:lun, and addresses the wrong device
> > 
> > While the current system doesn't prevent this, it makes it a much more
> > difficult situation to happen.
> 
> Surely the user would have to have known that one device was
> disconnected and another connected. Same thing could already be said for
> the scsi device allocation (sda, sdb, and sg0, sg1, sg2, etc...).

surely everyone is using cdrecord -dev=/dev/scd5  by now and not the 
host:bus:dev crap...

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-27  7:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  0:40 FWD: [BK PATCH] SCSI host num allocation improvement James Bottomley
2004-02-27  0:56 ` Matthew Dharm
2004-02-27  1:04   ` Ben Collins
2004-02-27  7:56     ` Arjan van de Ven [this message]
2004-02-27 12:30       ` Ben Collins
2004-02-27 12:39         ` Matthew Wilcox
2004-02-27 12:43           ` Ben Collins
2004-02-27 12:48             ` Christoph Hellwig
2004-02-27 12:48 ` Christoph Hellwig
2004-02-27 13:04   ` Ben Collins
2004-02-27 16:49     ` Mike Anderson
2004-02-27 17:00       ` Ben Collins
2004-02-27 21:26         ` Mike Anderson
2004-02-27 15:08   ` James Bottomley
2004-02-27 15:15     ` Ben Collins
2004-02-27 15:29       ` James Bottomley
2004-02-27 15:32         ` Ben Collins
2004-02-27 16:37           ` James Bottomley
2004-02-27 16:39             ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2004-02-27 13:25 David.Egolf

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=1077868581.4443.0.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=bcollins@debian.org \
    --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