aboutsummaryrefslogtreecommitdiffstats
path: root/include/scsi
diff options
context:
space:
mode:
author <axboe@suse.de>2005-04-12 16:22:06 -0500
committerJames Bottomley <jejb@titanic>2005-04-16 20:10:09 -0500
commit152587deb8903c0edf483a5b889f975bc6bea7e0 (patch)
tree62fc13bff0a28134adbb523ed1a2c0efdd9a85cb /include/scsi
parent56fece20086ebe32bce2c0d74ceadd516b56baae (diff)
downloadkernel_samsung_aries-152587deb8903c0edf483a5b889f975bc6bea7e0.zip
kernel_samsung_aries-152587deb8903c0edf483a5b889f975bc6bea7e0.tar.gz
kernel_samsung_aries-152587deb8903c0edf483a5b889f975bc6bea7e0.tar.bz2
[PATCH] fix NMI lockup with CFQ scheduler
The current problem seen is that the queue lock is actually in the SCSI device structure, so when that structure is freed on device release, we go boom if the queue tries to access the lock again. The fix here is to move the lock from the scsi_device to the queue. Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'include/scsi')
-rw-r--r--include/scsi/scsi_device.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/scsi/scsi_device.h b/include/scsi/scsi_device.h
index 07d9740..f6d0513 100644
--- a/include/scsi/scsi_device.h
+++ b/include/scsi/scsi_device.h
@@ -44,7 +44,6 @@ struct scsi_device {
struct list_head same_target_siblings; /* just the devices sharing same target id */
volatile unsigned short device_busy; /* commands actually active on low-level */
- spinlock_t sdev_lock; /* also the request queue_lock */
spinlock_t list_lock;
struct list_head cmd_list; /* queue of in use SCSI Command structures */
struct list_head starved_entry;