Re: [PATCH v12 2/6] Avoid calling __scsi_remove_device() twice

2013-07-01 Thread James Bottomley
On Mon, 2013-07-01 at 09:14 +0200, Bart Van Assche wrote: > On 07/01/13 09:05, James Bottomley wrote: > > > > On Thu, 2013-06-27 at 16:53 +0200, Bart Van Assche wrote: > >> If something goes wrong during LUN scanning, e.g. a transport layer > >> failure occurs, then __scsi_remove_device() can get i

Re: [PATCH v12 2/6] Avoid calling __scsi_remove_device() twice

2013-07-01 Thread Bart Van Assche
On 07/01/13 09:05, James Bottomley wrote: On Thu, 2013-06-27 at 16:53 +0200, Bart Van Assche wrote: If something goes wrong during LUN scanning, e.g. a transport layer failure occurs, then __scsi_remove_device() can get invoked by the LUN scanning code for a SCSI device in state SDEV_CREATED_BL

Re: [PATCH v12 2/6] Avoid calling __scsi_remove_device() twice

2013-07-01 Thread James Bottomley
On Thu, 2013-06-27 at 16:53 +0200, Bart Van Assche wrote: > If something goes wrong during LUN scanning, e.g. a transport layer > failure occurs, then __scsi_remove_device() can get invoked by the > LUN scanning code for a SCSI device in state SDEV_CREATED_BLOCK. If > this happens then the SCSI de

[PATCH v12 2/6] Avoid calling __scsi_remove_device() twice

2013-06-27 Thread Bart Van Assche
If something goes wrong during LUN scanning, e.g. a transport layer failure occurs, then __scsi_remove_device() can get invoked by the LUN scanning code for a SCSI device in state SDEV_CREATED_BLOCK. If this happens then the SCSI device has not yet been added to sysfs (is_visible == 0). Make sure