From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH] capabilities: add capability cgroup controller Date: Thu, 23 Jun 2016 17:38:19 -0400 Message-ID: <20160623213819.GP3262@mtj.duckdns.org> References: <1466694434-1420-1-git-send-email-toiwoton@gmail.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=KG3Y36jQFSVKIe+5RMabtdGQTu/XTv2PK9hj2hB8Qqk=; b=A3a/IHJiNWOKGPP7i2VLHm7FI2cyT3ohH6bWXb9IfwRUKVx1B5ilKQAe/YUn2LgDCW 0huRmIwYvSvTrYjrbMBfByvbo/t6iaPrVKDFWM3goAy7jgjeJ1axddG1BK7PnHfPg1Oq 7ESpLLzV3OQ2tBTP7c8vGw1eOYhbty05oMA+6vigrnBmOKHNZEvuteBGEWb8HOYGpb1v WIoCNOgdBrAaa/iUN1YqB1ABFxbJEFdkCWafcbqxY7qbTFBpf9p4T0RwqP9b5C6UZgIi zbb+h3GwwASBPGjZCmm4Dpbk09GtF0LZuwLtJ69nE73IaRlu0N60AAbjrCRmCUC1BZAa J12g== Content-Disposition: inline In-Reply-To: <1466694434-1420-1-git-send-email-toiwoton@gmail.com> Sender: linux-doc-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Topi Miettinen Cc: linux-kernel@vger.kernel.org, luto@kernel.org, serge@hallyn.com, keescook@chromium.org, Jonathan Corbet , Li Zefan , Johannes Weiner , Serge Hallyn , James Morris , Andrew Morton , David Howells , David Woodhouse , Ard Biesheuvel , "Paul E. McKenney" , Petr Mladek , "open list:DOCUMENTATION" , "open list:CONTROL GROUP (CGROUP)" , "open list:CAPABILITIES" Hello, On Thu, Jun 23, 2016 at 06:07:10PM +0300, Topi Miettinen wrote: > There are many basic ways to control processes, including capabilities, > cgroups and resource limits. However, there are far fewer ways to find > out useful values for the limits, except blind trial and error. > > Currently, there is no way to know which capabilities are actually used. > Even the source code is only implicit, in-depth knowledge of each > capability must be used when analyzing a program to judge which > capabilities the program will exercise. > > Add a new cgroup controller for monitoring of capabilities > in the cgroup. > > Test case demonstrating basic capability monitoring and how the > capabilities are combined at next level (boot to rdshell): This doesn't have anything to do with resource control and I don't think it's a good idea to add arbitrary monitoring mechanisms to cgroup just because it's easy to add interface there. Given that capabilities are inherited and modified through the process hierarchy, shouldn't this be part of that? Thanks. -- tejun