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 10:37:13 -0600 [thread overview]
Message-ID: <1077899833.2157.82.camel@mulgrave> (raw)
In-Reply-To: <20040227153247.GL4019@phunnypharm.org>
On Fri, 2004-02-27 at 09:32, Ben Collins wrote:
> On the same token, if you hot plug/unplug a single device (not a host)
> on the same host, you will already have this problem. This wont make the
> problem any worse or better. Devices are more likely to get
> plugged/unplugged anyway (well, in the case of usb/firewire you
> plug/unplug a host/dev combination, but still).
Simply having races is not an excuse for introducing more, particularly
when they're under our control.
This represents a behaviour change in a stable kernel introducing a
potential problem in hotplug and solving a fixable issue in a single
user application tool.
What I'm not yet convinced of is that the benefits outweigh the risks.
James
next prev parent reply other threads:[~2004-02-27 16:37 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
2004-02-27 15:32 ` Ben Collins
2004-02-27 16:37 ` James Bottomley [this message]
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=1077899833.2157.82.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