* Brian King (brk...@linux.vnet.ibm.com) wrote:
> 
> No locks should be held when calling scsi_adjust_queue_depth
> so drop the lock in slave_configure prior to calling it.
> 
> Signed-off-by: Brian King <brk...@linux.vnet.ibm.com>
Acked-by: Robert Jennings <r...@linux.vnet.ibm.com>
> ---
> 
>  drivers/scsi/ibmvscsi/ibmvscsi.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN drivers/scsi/ibmvscsi/ibmvscsi.c~ibmvscsi_slave_configure_deadlock 
> drivers/scsi/ibmvscsi/ibmvscsi.c
> --- linux/drivers/scsi/ibmvscsi/ibmvscsi.c~ibmvscsi_slave_configure_deadlock  
> 2013-03-06 16:36:26.000000000 -0600
> +++ linux-bjking1/drivers/scsi/ibmvscsi/ibmvscsi.c    2013-03-06 
> 16:36:26.000000000 -0600
> @@ -1899,8 +1899,8 @@ static int ibmvscsi_slave_configure(stru
>               sdev->allow_restart = 1;
>               blk_queue_rq_timeout(sdev->request_queue, 120 * HZ);
>       }
> -     scsi_adjust_queue_depth(sdev, 0, shost->cmd_per_lun);
>       spin_unlock_irqrestore(shost->host_lock, lock_flags);
> +     scsi_adjust_queue_depth(sdev, 0, shost->cmd_per_lun);
>       return 0;
>  }
> 
> _

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to