[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWcQtLTVJU14ytWxu_gqoLuAYZJpyAvRsKwwgYZz7FEFg@mail.gmail.com>
Date: Sun, 30 Sep 2018 21:45:44 -0700
From: Andy Lutomirski <luto@...nel.org>
To: laurent@...ier.eu
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
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?
Powered by blists - more mailing lists