From: James Bottomley <James.Bottomley@SteelEye.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Mark Lord <lsml@rtr.ca>, Anton Blanchard <anton@samba.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Core scsi layer crashes in 2.6.8.1
Date: 05 Oct 2004 11:07:31 -0500 [thread overview]
Message-ID: <1096992458.2173.35.camel@mulgrave> (raw)
In-Reply-To: <200410051801.03677.oliver@neukum.org>
On Tue, 2004-10-05 at 11:01, Oliver Neukum wrote:
> Why is it in any way difficult to decide whether to issue a command in the
> first place? The command is generated upon being notified by the lower layer.
> There is no issue of synchronisation here. It is simply stupid to give
> commands that are bound to fail, if the information is already available.
a) we don't know that they are ... for notified ejection they will
succeed.
b) The scsi bus is a scanned model ... drivers must be prepared to
accept commands for non-existent devices. How does the removal case
differ from the never present case?
James
next prev parent reply other threads:[~2004-10-05 16:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:03 Core scsi layer crashes in 2.6.8.1 Alan Cox
2004-09-29 14:11 ` James Bottomley
2004-09-29 13:24 ` Alan Cox
2004-09-29 14:34 ` James Bottomley
2004-09-29 14:27 ` Matthew Wilcox
2004-10-05 11:49 ` Anton Blanchard
2004-10-05 13:56 ` James Bottomley
2004-10-05 14:44 ` Mark Lord
2004-10-05 14:56 ` James Bottomley
2004-10-05 15:46 ` Mark Lord
2004-10-05 15:49 ` Oliver Neukum
2004-10-05 15:54 ` James Bottomley
2004-10-05 15:57 ` Mark Lord
2004-10-05 16:01 ` James Bottomley
2004-10-05 16:53 ` Jeff Garzik
2004-10-05 16:01 ` Oliver Neukum
2004-10-05 16:07 ` James Bottomley [this message]
2004-10-05 16:26 ` Oliver Neukum
2004-10-05 16:38 ` James Bottomley
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=1096992458.2173.35.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsml@rtr.ca \
--cc=oliver@neukum.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