If you imagine that KHO is destructive then every failure point needs to unwind the partial destruction which is a total nightmare to code :\ > Main idea is for logical grouping and dependency management. If some FDs > have a dependency between them, grouping them in different boxes makes > it easy to let userspace choose the order of operations, but still have > a way to make sure all dependencies are met when the FDs are serialized. > Similarly, on the deserialize side, this ensures that all dependent FDs > are deserialized together. That seems over complicated to me. Userspace should write the FDs in the required order and that should be a topological sort of the required dependencies. kernel should just validate this was done. Jason
