[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <564D7FF6.50408@nod.at>
Date: Thu, 19 Nov 2015 08:53:26 +0100
From: Richard Weinberger <richard@....at>
To: James Morris <jmorris@...ei.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Seth Forshee <seth.forshee@...onical.com>,
Austin S Hemmelgarn <ahferroin7@...il.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-bcache@...r.kernel.org,
device-mapper development <dm-devel@...hat.com>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LSM <linux-security-module@...r.kernel.org>,
selinux@...ho.nsa.gov, Serge Hallyn <serge.hallyn@...onical.com>,
Andy Lutomirski <luto@...capital.net>,
LKML <linux-kernel@...r.kernel.org>,
Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH v3 0/7] User namespace mount updates
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 <viro@...iv.linux.org.uk> 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.
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists