[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25217d8b-f3e9-7362-e3d9-d8c37bf39558@infradead.org>
Date: Tue, 11 Feb 2020 09:26:17 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Christian Brauner <christian.brauner@...ntu.com>,
Stéphane Graber <stgraber@...ntu.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Aleksa Sarai <cyphar@...har.com>, Jann Horn <jannh@...gle.com>
Cc: smbarber@...omium.org, Alexander Viro <viro@...iv.linux.org.uk>,
Alexey Dobriyan <adobriyan@...il.com>,
Serge Hallyn <serge@...lyn.com>,
James Morris <jmorris@...ei.org>,
Kees Cook <keescook@...omium.org>,
Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
containers@...ts.linux-foundation.org,
linux-security-module@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH 01/24] user_namespace: introduce fsid mappings
infrastructure
On 2/11/20 8:57 AM, Christian Brauner wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index a34064a031a5..4da082e4f787 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1102,6 +1102,17 @@ config USER_NS
>
> If unsure, say N.
>
> +config USER_NS_FSID
> + bool "User namespace fsid mappings"
> + depends on USER_NS
> + default n
> + help
> + This allows containers, to alter their filesystem id mappings.
no comma ^^^^
> + With this containers with different id mappings can still share
> + the same filesystem.
> +
> + If unsure, say N.
> +
> config PID_NS
> bool "PID Namespaces"
> default y
--
~Randy
Powered by blists - more mailing lists