From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751757Ab2IPNcb (ORCPT ); Sun, 16 Sep 2012 09:32:31 -0400 Received: from 50-56-35-84.static.cloud-ips.com ([50.56.35.84]:58474 "EHLO mail.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750845Ab2IPNc3 (ORCPT ); Sun, 16 Sep 2012 09:32:29 -0400 Message-ID: <5055D4D1.3070407@hallyn.com> Date: Sun, 16 Sep 2012 08:32:01 -0500 From: Serge Hallyn User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "Eric W. Biederman" CC: Alan Cox , Aristeu Rozanski , Neil Horman , "Serge E. Hallyn" , containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Michal Hocko , Thomas Graf , Paul Mackerras , "Aneesh Kumar K.V" , Arnaldo Carvalho de Melo , Johannes Weiner , Tejun Heo , cgroups@vger.kernel.org, Paul Turner , Ingo Molnar Subject: Re: Controlling devices and device namespaces References: <20120913205827.GO7677@google.com> <20120914183641.GA2191@cathedrallabs.org> <20120915022037.GA6438@mail.hallyn.com> <87wqzv7i08.fsf_-_@xmission.com> <20120915220520.GA11364@mail.hallyn.com> <87y5kazuez.fsf@xmission.com> <20120916122112.3f16178d@pyramind.ukuu.org.uk> <87sjaiuqp5.fsf@xmission.com> <87d31mupp3.fsf@xmission.com> In-Reply-To: <87d31mupp3.fsf@xmission.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/16/2012 07:17 AM, Eric W. Biederman wrote: > ebiederm@xmission.com (Eric W. Biederman) writes: > >> Alan Cox writes: >> >>>> One piece of the puzzle is that we should be able to allow unprivileged >>>> device node creation and access for any device on any filesystem >>>> for which it unprivileged access is safe. >>> >>> Which devices are "safe" is policy for all interesting and useful cases, >>> as are file permissions, security tags, chroot considerations and the >>> like. >>> >>> It's a complete non starter. > > Come to think of it mknod is completely unnecessary. > > Without mknod. Without being able to mount filesystems containing > device nodes. Hm? That sounds like it will really upset init/udev/upgrades in the container. Are you saying all filesystems containing device nodes will need to be mounted in advance by the process setting up the container? > The mount namespace is sufficient to prevent all of the > cases that the device control group prevents (open and mknod on device > nodes). > > So I honestly think the device control group is superflous, and it is > probably wise to deprecate it and move to a model where it does not > exist. > > Eric > That's what I said a few emails ago :) The device cgroup was meant as a short-term workaround for lack of user (and device) namespaces.