Paul Menage wrote: > On Wed, Jul 9, 2008 at 11:54 PM, Nadia Derbey <[EMAIL PROTECTED]> wrote: > >>Don't you think it's simpler to specify the target fd, and then open the >>file. > > > Maybe. But: > > - this can already be done without extra kernel support, via open() > followed by dup2()
Sure, I completely agree with you. Actually, that's the way it is handled in cryo code. But I think that both ways of doing are not exactly the same in case of failure: open + dup2 will close newfd if it is already busy. while next-syscall_data + open will fail if the target fd is already busy. And that's the functionality we need during restart, isn't it? Regards, Nadia > > - if you were going to add it to the kernel, the precedent set by > openat() is that you create a new system call that supports the > extended semantics. > > _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
