Hi Christoph,
never checked anywhere Index: linux-2.6/drivers/scsi/scsi.c =================================================================== --- linux-2.6.orig/drivers/scsi/scsi.c 2005-06-19 12:03:42.000000000 +0200 +++ linux-2.6/drivers/scsi/scsi.c 2005-06-19 12:27:27.000000000 +0200 @@ -258,7 +258,6 @@ memset(cmd, 0, sizeof(*cmd)); cmd->device = dev; cmd->state = SCSI_STATE_UNUSED; - cmd->owner = SCSI_OWNER_NOBODY; init_timer(&cmd->eh_timeout); INIT_LIST_HEAD(&cmd->list); spin_lock_irqsave(&dev->list_lock, flags); @@ -610,7 +609,6 @@ */
I think these field(owner & state) are usefull to analyze the SCSI trouble with kernel memory dump. Do we have another way to identify which layer is processing the scsi_cmnd?
Hironobu Ishii - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
