[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1b6b52b-dd7f-fa27-eafa-7a6a43a03b92@vivier.eu>
Date: Mon, 1 Oct 2018 09:13:41 +0200
From: Laurent Vivier <laurent@...ier.eu>
To: Andy Lutomirski <luto@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Al Viro <viro@...iv.linux.org.uk>,
Linux API <linux-api@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Dmitry Safonov <dima@...sta.com>,
Andrey Vagin <avagin@...nvz.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC 0/2] ns: introduce binfmt_misc namespace
Le 01/10/2018 à 06:45, Andy Lutomirski a écrit :
> On Sun, Sep 30, 2018 at 4:47 PM Laurent Vivier <laurent@...ier.eu> wrote:
>>
>> This series introduces a new namespace for binfmt_misc.
>>
>
> This seems conceptually quite reasonable, but I'm wondering if the
> number of namespace types is getting out of hand given the current
> API. Should we be considering whether we need a new set of namespace
> creation APIs that scale better to larger numbers of namespace types?
>
Yes, we need something to increase the maximum number of namespace types
because this is the last bit in the clone() flags and the time namespace
has already preempted it.
Thanks,
Laurent
Powered by blists - more mailing lists