On Thu, 2013-06-27 at 16:54 +0200, Bart Van Assche wrote: > Restrict the SCSI device state changes allowd via sysfs to the > OFFLINE<>RUNNING transitions. Other transitions may confuse > the SCSI mid-layer. As an example, changing the state of a SCSI > device via sysfs into "cancel" or "deleted" prevents removal of > a SCSI device by scsi_remove_host().
This one's not ready for application. I would like a debate on what we should be doing. Currently we don't apply any sanity checking at all. Should we? And should we police user state changes. If so, What changes should we allow? I opine that really only OFFLINE <-> RUNNING make sense, but I've no idea what people actually use this field for (if they use it at all). James -- 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
