On Fri, Apr 06, 2012 at 01:41:06PM -0700, Dan Williams wrote: > In scsi at least two cases of the parent device being deleted before the > child is added have been observed. > > 1/ scsi is performing async scans and the device is removed prior to the > async can thread running (can happen with an in-opportune / unlikely > unplug during initial scan). That sounds like a bug in the scsi code, doesn't it? > 2/ libsas discovery event running after the parent port has been torn > down (this is a bug in libsas). Is this fixed somewhere? I don't want to paper over bugs like this by changing the sysfs core. We went through this a lot years ago when scsi changed to use the driver core, and I thought we had fixed all of these types of errors properly. So, any chance to fix these properly as well? thanks, greg k-h -- To unsubscribe from this list: 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
