On Thu, 2008-07-10 at 10:54 +0200, Pavel Machek wrote: > > If you don't see a backward compatibility problem here, perhaps you > should not be hacking kernel...? The way ids are assigned is certainly > part of syscall semantics (applications rely on), at least for open.
We also used to have a pretty defined ordering for handing out address space with mmap(). That all changed with address space randomization. Are file descriptors different somehow? Anyway, it's not like we're actually changing existing behavior. An application has to do something special and new to trigger this new behavior. Nobody is going to stumble over it, and it will *not* break backward compatibility. -- Dave _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
