[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWM7JupEWeyT5OUDozGG1-XMVpAX+Ah5QwiX+G0VyveDA@mail.gmail.com>
Date: Mon, 13 Jun 2016 13:32:21 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Topi Miettinen <toiwoton@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Serge Hallyn <serge.hallyn@...onical.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Christoph Lameter <cl@...ux.com>,
"Serge E. Hallyn" <serge.hallyn@...ntu.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"Richard W.M. Jones" <rjones@...hat.com>,
Iago López Galeiras <iago@...ocode.com>,
Chris Metcalf <cmetcalf@...hip.com>,
Andy Lutomirski <luto@...nel.org>, Jann Horn <jann@...jh.net>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@...r.kernel.org>,
"open list:CAPABILITIES" <linux-security-module@...r.kernel.org>
Subject: Re: [RFC 01/18] capabilities: track actually used capabilities
On Mon, Jun 13, 2016 at 12:44 PM, Topi Miettinen <toiwoton@...il.com> wrote:
> Track what capabilities are actually used and present the current
> situation in /proc/self/status.
What for?
What is the intended behavior on fork()? Whatever the intended
behavior is, there should IMO be a selftest for it.
--Andy
Powered by blists - more mailing lists