From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932527AbaJVTmJ (ORCPT ); Wed, 22 Oct 2014 15:42:09 -0400 Received: from mail-qg0-f48.google.com ([209.85.192.48]:58615 "EHLO mail-qg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754296AbaJVTmG (ORCPT ); Wed, 22 Oct 2014 15:42:06 -0400 Date: Wed, 22 Oct 2014 15:42:00 -0400 From: Tejun Heo To: Aditya Kali Cc: Andy Lutomirski , "Eric W. Biederman" , "Serge E. Hallyn" , Linux API , Linux Containers , Serge Hallyn , "linux-kernel@vger.kernel.org" , cgroups@vger.kernel.org, Ingo Molnar Subject: Re: [PATCHv1 7/8] cgroup: cgroup namespace setns support Message-ID: <20141022194200.GA24009@htj.dyndns.org> References: <87lhoayo59.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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//cgroup does not show > relative paths today. This is also very ambiguous (is it relative to > cgroupns-root or relative to /proc/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