From: James Bottomley <James.Bottomley@steeleye.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Calling sd_shutdown when in state SDEV_DEL
Date: 24 Mar 2004 10:35:03 -0500 [thread overview]
Message-ID: <1080142505.2706.25.camel@mulgrave> (raw)
In-Reply-To: <200403241603.23269.heiko.carstens@de.ibm.com>
On Wed, 2004-03-24 at 10:03, Heiko Carstens wrote:
> upon scsi_remove_device the sd driver tries to send out a SYNCHRONIZE_CACHE
> command (sd_shutdown) which is not possible because the sdev_state for the
> device in question is already SDEV_DEL.
> The patch below solves the problem, but I'm not sure if this is the right
> way to do it. Also setting the state to SDEV_DEL after calling device_del
> is probably pointless...
Actually, I don't think quiesce, because that defers I/O waiting to
restart (also the transition QUIESCE->DEL is currently forbidden).
How about the attached instead. That forces every deleted device to go
through CANCEL (uncompiled, but you can test it...)
James
===== scsi_sysfs.c 1.43 vs edited =====
--- 1.43/drivers/scsi/scsi_sysfs.c Sat Mar 13 07:09:30 2004
+++ edited/scsi_sysfs.c Wed Mar 24 10:32:56 2004
@@ -436,18 +436,19 @@
**/
void scsi_remove_device(struct scsi_device *sdev)
{
- if (sdev->sdev_state == SDEV_RUNNING || sdev->sdev_state == SDEV_CANCEL) {
- scsi_device_set_state(sdev, SDEV_DEL);
- class_device_unregister(&sdev->sdev_classdev);
- if(sdev->transport_classdev.class)
- class_device_unregister(&sdev->transport_classdev);
- device_del(&sdev->sdev_gendev);
- if (sdev->host->hostt->slave_destroy)
- sdev->host->hostt->slave_destroy(sdev);
- if (sdev->host->transportt->cleanup)
- sdev->host->transportt->cleanup(sdev);
- put_device(&sdev->sdev_gendev);
- }
+ if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
+ return;
+
+ class_device_unregister(&sdev->sdev_classdev);
+ if(sdev->transport_classdev.class)
+ class_device_unregister(&sdev->transport_classdev);
+ device_del(&sdev->sdev_gendev);
+ scsi_device_set_state(sdev, SDEV_DEL);
+ if (sdev->host->hostt->slave_destroy)
+ sdev->host->hostt->slave_destroy(sdev);
+ if (sdev->host->transportt->cleanup)
+ sdev->host->transportt->cleanup(sdev);
+ put_device(&sdev->sdev_gendev);
}
int scsi_register_driver(struct device_driver *drv)
next prev parent reply other threads:[~2004-03-24 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 15:03 Calling sd_shutdown when in state SDEV_DEL Heiko Carstens
2004-03-24 15:35 ` James Bottomley [this message]
2004-03-24 16:28 ` Heiko Carstens
2004-03-24 17:04 ` Mike Anderson
2004-03-24 20:09 ` James Bottomley
2004-03-25 1:48 ` Mike Anderson
2004-04-02 23:33 ` James Bottomley
2004-03-24 16:46 ` Mike Anderson
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=1080142505.2706.25.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=heiko.carstens@de.ibm.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