From: Ben Collins <bcollins@debian.org>
To: Arjan van de Ven <arjanv@redhat.com>
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 07:30:09 -0500 [thread overview]
Message-ID: <20040227123009.GD4019@phunnypharm.org> (raw)
In-Reply-To: <1077868581.4443.0.camel@laptop.fenrus.com>
On Fri, Feb 27, 2004 at 08:56:22AM +0100, Arjan van de Ven wrote:
> 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...
scsidev: '/dev/sg1'
devname: '/dev/sg1'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-02-27 12:31 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
2004-02-27 12:30 ` Ben Collins [this message]
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=20040227123009.GD4019@phunnypharm.org \
--to=bcollins@debian.org \
--cc=James.Bottomley@steeleye.com \
--cc=arjanv@redhat.com \
--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