Hi Jessica, > One of the benefits of having a new clone3 is that the interface can be > made the same across all architectures*, unlike clone, which both passes > the arguments in different orders for different architectures and, in > the case of SPARC, has this weird return convention inherited from the > SunOS syscall interface. Is there a good reason to deviate for clone3 > too and keep this annoying oddity going, that requires special-casing > SPARC when other architectures can just syscall(__NR_clone3, ...)? >
Thanks for commenting on this. No, you're right (there is no good reason). The original implementation just followed how things were but I have a v2 coming up which will follow the regular kernel return value conventions. This will ensure that syscall(__NR_clone3, ...) works on SPARC exactly as it does on other architectures (i.e I'll drop the third patch in the series). Best regards, // Ludwig
