Or to put it the other way around - why even start an operation that will fail? We have a pretty similar issue in file system land: A file system must handle failure from the storage device at any time to provide data integrity. But that doesn't mean we can't optimize for the case where a device is toast (host removed, fails any I/O, etc). In that case we mark the file system as shutdown and stop submitting more I/O, potentially avoiding up to hours of recovery time. It would be helpful for everyone up and down the stack to do these don't do anyting stupid if you can avoid it starting from the lowest layers. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
