Hi, Cephers: What if a spawned stack fails? In RGWCoroutinesManager::run(), the loop traversing stacks will not break when a spawned stack fails and this function just return the last stack's operate value or zero when any blocked stack occurs. In drain_all() macro, the failure info of a spawned stack is discarded. Only RGWCoroutine::collect() function cares about stack's return value, but this function can not capture all stack's failure info. For example, in RGWInitSyncStatusCoroutine::operate(), the drain_all() macro is called after a collect() function. If a spawned stack finishes after the collect() function and fails, that failure info is lost. Is this an anticipated behavior? Thanks. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
