public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Ben Collins <bcollins@debian.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: FWD: [BK PATCH] SCSI host num allocation improvement
Date: 27 Feb 2004 09:29:34 -0600	[thread overview]
Message-ID: <1077895775.2157.22.camel@mulgrave> (raw)
In-Reply-To: <20040227151551.GK4019@phunnypharm.org>

On Fri, 2004-02-27 at 09:15, Ben Collins wrote:
> If a driver somehow removes it's scsi host and then later attempts a
> scsi_host_lookup for the id, I think that driver is broken anyway. IOW,
> it is safe as long as you aren't broken in the first place.

I'm not thinking about the driver, I'm thinking about the hotplug
system.  Hotplug events are queued and not locked.  The event identifies
the scsi device by the (host number, channel number, target, lun)
quadruple.  The reason it has to do that is that the /proc/scsi/scsi
add/remove device operate on these numbers.

If we get a sequence of racing connects and disconnects, we could mis
identify the devices because of the host number reuse.  That's the race
I want assurance of making safe if we move to reusing the numbers.

Obviously, one solution would be to fix the /proc add/remove, but it's a
bit late in 2.6 to change the interface, I think.

James



  reply	other threads:[~2004-02-27 15:29 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
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 [this message]
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=1077895775.2157.22.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=bcollins@debian.org \
    --cc=hch@infradead.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