Hello, On Wed, Oct 22, 2014 at 11:37:55AM -0700, Aditya Kali wrote: ... > Actually, there is no right answer here. Our options are: > * show relative path > -- this will break userspace as /proc/<pid>/cgroup does not show > relative paths today. This is also very ambiguous (is it relative to > cgroupns-root or relative to /proc/<pid>cgroup file reader's cgroup?). Let's go with this w/o pinning. The only necessary feature for cgroupns is making the /proc/*/cgroups relative to its own root. It's not like containers can avoid trusting its outside world anyway and playing tricks with things like this tend to lead to weird surprises down the road. If userland messes up, userland messes up. Thanks. -- tejun _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
