Can somebody explain the reason for calling a separate 
scsi_sysfs_add_devices() routine in the async scanning code instead of 
just calling scsi_sysfs_add_sdev() normally from within scsi_add_lun()?

This peculiar delayed approach has introduced a bug.  It evades the
protection provided by shost->scan_mutex and as a result, if a host is
hot-unplugged in the middle of an async scan, the SCSI core will
attempt to unregister the host's devices before they have been
registered!  Obviously this is not good.

There are at least two reports filed in the kernel.org bugilla showing 
this bug: #8840 and #8846.

Alan Stern

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

Reply via email to