Re: [PATCH] capabilities: add capability cgroup controller
From: "Serge E. Hallyn" <serge@hallyn.com>
Date: 2016-06-27 14:55:03
Also in:
lkml
From: "Serge E. Hallyn" <serge@hallyn.com>
Date: 2016-06-27 14:55:03
Also in:
lkml
Quoting Tejun Heo (tj@kernel.org):
Hello, Topi. On Sun, Jun 26, 2016 at 3:14 PM, Topi Miettinen [off-list ref] wrote:quoted
The parent might be able do it if proc/pid/xyz files are still accessible after child exit but before its exit status is collected. But if the parent doesn't do it (and you are not able to change it to do it) and it collects the exit status without collecting other info, can you suggest a different way how another process could collect it 100% reliably?I'm not saying that there's such mechanism now. I'm suggesting that that'd be a more fitting way of implementing a new mechanism to track capability usages.
Hi Topi, I think Eric was right a few emails earlier that the audit subsystem is really the most appropriate answer to this. (Perhaps sysctl-controllered?) Combined with taskstats it would give you what you need. Or you could even use an empty new named cgroup controller, say 'none,name=caps', and then look only at audit results for cgroup '/myapp' in the caps hierarchy.