From: akpm@linux-foundation.org
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, akpm@linux-foundation.org,
kuznet@ms2.inr.ac.ru, alan@lxorguk.ukuu.org.uk, den@openvz.org,
stern@rowland.harvard.edu
Subject: [patch for 2.6.32? 3/3] scsi: fix another crash at disconnect of usb strorage
Date: Tue, 17 Nov 2009 14:10:13 -0800 [thread overview]
Message-ID: <200911172210.nAHMADAW014298@imap1.linux-foundation.org> (raw)
From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Asynchronous scan (scsi_add_lun()) sets state to SDEV_RUNNING, but the
device is not registered in sysfs. Before async scan it was OK, because
before releasing scan_mutex old code called either scsi_sysfs_add_sdev()
or scsi_destroy_sdev() and, therefore, completed the work or discarded it.
With async scan the invariant is broken and scsi crashes in
__scsi_remove_device() when trying to unregister not registered devices.
The fix could be introducing new state(s), which is equivalent to
SDEV_RUNNING, except for one thing, we know that scsi_sysfs_add_sdev() has
not been called yet. Or a separate flag, because the state can be
SDEV_BLOCK or even something else.
Simpler way is just to check that the device is regstered in sysfs before
unregistering. Another operations in __scsi_remove_device() seem to be
idempotent or even required, because scsi_add_lun() makes some part of
work duplicated in scsi_sysfs_add_sdev().
Signed-off-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: Denis V. Lunev <den@openvz.org>
Cc: Alan Stern <stern@rowland.harvard.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/scsi/scsi_sysfs.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff -puN drivers/scsi/scsi_sysfs.c~scsi-fix-another-crash-at-disconnect-of-usb-strorage drivers/scsi/scsi_sysfs.c
--- a/drivers/scsi/scsi_sysfs.c~scsi-fix-another-crash-at-disconnect-of-usb-strorage
+++ a/drivers/scsi/scsi_sysfs.c
@@ -965,9 +965,17 @@ void __scsi_remove_device(struct scsi_de
return;
bsg_unregister_queue(sdev->request_queue);
- device_unregister(&sdev->sdev_dev);
+ /* Asynchronous scan violates invariant that SDEV_RUNNING
+ * implies that device is registered in sysfs.
+ * We could introduce new state flag or extend set of state,
+ * but just plain checking that device is registered already
+ * before trying to unregister it is enough.
+ */
+ if (sdev->sdev_dev.kobj.parent)
+ device_unregister(&sdev->sdev_dev);
transport_remove_device(dev);
- device_del(dev);
+ if (dev->kobj.parent)
+ device_del(dev);
scsi_device_set_state(sdev, SDEV_DEL);
if (sdev->host->hostt->slave_destroy)
sdev->host->hostt->slave_destroy(sdev);
_
next reply other threads:[~2009-11-17 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 22:10 akpm [this message]
2009-11-17 22:44 ` [patch for 2.6.32? 3/3] scsi: fix another crash at disconnect of usb strorage Alan Stern
2009-11-19 12:59 ` Alexey Kuznetsov
2009-11-19 17:57 ` Alan Stern
2009-11-20 17:26 ` 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=200911172210.nAHMADAW014298@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=den@openvz.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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