Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758638AbbKSOVS (ORCPT ); Thu, 19 Nov 2015 09:21:18 -0500 Received: from h2.hallyn.com ([78.46.35.8]:35438 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757862AbbKSOVP (ORCPT ); Thu, 19 Nov 2015 09:21:15 -0500 Date: Thu, 19 Nov 2015 08:21:13 -0600 From: "Serge E. Hallyn" To: Richard Weinberger Cc: James Morris , Al Viro , Seth Forshee , Austin S Hemmelgarn , "Eric W. Biederman" , linux-bcache@vger.kernel.org, device-mapper development , "linux-raid@vger.kernel.org" , "linux-mtd@lists.infradead.org" , linux-fsdevel , LSM , selinux@tycho.nsa.gov, Serge Hallyn , Andy Lutomirski , LKML , "Theodore Ts'o" Subject: Re: [PATCH v3 0/7] User namespace mount updates Message-ID: <20151119142113.GA5607@mail.hallyn.com> References: <564B941A.2070601@gmail.com> <20151117213255.GE108807@ubuntu-hedt> <564C6DD4.6090308@gmail.com> <20151118142238.GB134139@ubuntu-hedt> <20151118145818.GC22011@ZenIV.linux.org.uk> <20151118150512.GE134139@ubuntu-hedt> <20151118151335.GD22011@ZenIV.linux.org.uk> <564D7FF6.50408@nod.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <564D7FF6.50408@nod.at> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1324 Lines: 28 On Thu, Nov 19, 2015 at 08:53:26AM +0100, Richard Weinberger wrote: > Am 19.11.2015 um 08:47 schrieb James Morris: > > On Wed, 18 Nov 2015, Richard Weinberger wrote: > > > >> On Wed, Nov 18, 2015 at 4:13 PM, Al Viro wrote: > >>> On Wed, Nov 18, 2015 at 09:05:12AM -0600, Seth Forshee wrote: > >>> > >>>> Yes, the host admin. I'm not talking about trusting the admin inside the > >>>> container at all. > >>> > >>> Then why not have the same host admin just plain mount it when setting the > >>> container up and be done with that? From the host namespace, before spawning > >>> the docker instance or whatever framework you are using. IDGI... > >> > >> Because hosting companies sell containers as "full virtual machines" > >> and customers expect to be able mount stuff like disk images they upload. > > > > I don't think this is a valid reason for merging functionality into the > > kernel. > > Erm, I don't want this in the kernel. That's why I've proposed the lklfuse approach. That would require the fuse-in-containers functionality, right? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/