From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1423179AbcFMUco (ORCPT <rfc822;w@1wt.eu>);
	Mon, 13 Jun 2016 16:32:44 -0400
Received: from mail-oi0-f52.google.com ([209.85.218.52]:33810 "EHLO
	mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1161373AbcFMUcm (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 13 Jun 2016 16:32:42 -0400
MIME-Version: 1.0
In-Reply-To: <1465847065-3577-2-git-send-email-toiwoton@gmail.com>
References: <1465847065-3577-1-git-send-email-toiwoton@gmail.com> <1465847065-3577-2-git-send-email-toiwoton@gmail.com>
From: Andy Lutomirski <luto@amacapital.net>
Date: Mon, 13 Jun 2016 13:32:21 -0700
Message-ID: <CALCETrWM7JupEWeyT5OUDozGG1-XMVpAX+Ah5QwiX+G0VyveDA@mail.gmail.com>
Subject: Re: [RFC 01/18] capabilities: track actually used capabilities
To: Topi Miettinen <toiwoton@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>,
        Serge Hallyn <serge.hallyn@canonical.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Kees Cook <keescook@chromium.org>, Christoph Lameter <cl@linux.com>,
        "Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
        Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
        "Richard W.M. Jones" <rjones@redhat.com>,
        =?UTF-8?Q?Iago_L=C3=B3pez_Galeiras?= <iago@endocode.com>,
        Chris Metcalf <cmetcalf@ezchip.com>, Andy Lutomirski <luto@kernel.org>,
        Jann Horn <jann@thejh.net>,
        "open list:FILESYSTEMS (VFS and infrastructure)" 
	<linux-fsdevel@vger.kernel.org>,
        "open list:CAPABILITIES" <linux-security-module@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Jun 13, 2016 at 12:44 PM, Topi Miettinen <toiwoton@gmail.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