[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF2d9jihrtUs870+K19zQWtvA4WOkX6ZfKC0BGTt1FQ3NVfxww@mail.gmail.com>
Date: Wed, 24 Aug 2016 17:28:48 -0700
From: Mahesh Bandewar (महेश बंडेवार)
<maheshb@...gle.com>
To: Parav Pandit <pandit.parav@...il.com>
Cc: Anoop Naravaram <anaravaram@...gle.com>,
Jonathan Corbet <corbet@....net>, Tejun Heo <tj@...nel.org>,
lizefan@...wei.com, Johannes Weiner <hannes@...xchg.org>,
David Miller <davem@...emloft.net>, kuznet@....inr.ac.ru,
jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net,
linux-doc@...r.kernel.org, cgroups@...r.kernel.org,
linux-netdev <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Wei Wang <weiwan@...gle.com>, tom@...bertland.com
Subject: Re: [PATCH 0/5] Networking cgroup controller
On Tue, Aug 23, 2016 at 1:49 AM, Parav Pandit <pandit.parav@...il.com> wrote:
> Hi Anoop,
>
> Regardless of usecase, I think this functionality is best handled as
> LSM functionality instead of cgroup.
>
I'm not so sure about that. Cgroup APIs are useful and this is just an
extension to it.
> Tasks which are proposed in this patch are related to access control checks.
> LSM already has required hooks for socket operations such as bind(),
> listen() as few small examples.
>
> Refer to security_socket_listen() which invokes LSM specific hooks.
> This is invoked in source/net/socket.c as part of listen() system call.
> LSM hook callback can check whether a given a process can listen to
> requested UDP port or not.
>
This has administrative overhead that is not addressed. The underlying
cgroup infrastructure takes care of it in this (current)
implementation.
> Parav
>
>
[...]
Powered by blists - more mailing lists