[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrU3jbtb6MqKHSwo=5PLoDi09HVdb=254kK++ezpCfcK6g@mail.gmail.com>
Date: Tue, 19 May 2015 13:23:50 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Aaron Jones <aaronmdjones@...il.com>
Cc: Christoph Lameter <cl@...ux.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
"Ted Ts'o" <tytso@....edu>, "Andrew G. Morgan" <morgan@...nel.org>,
Andrew Morton <akpm@...uxfoundation.org>,
Serge Hallyn <serge.hallyn@...ntu.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Linux API <linux-api@...r.kernel.org>,
Austin S Hemmelgarn <ahferroin7@...il.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Serge Hallyn <serge.hallyn@...onical.com>,
Markku Savela <msa@...h.iki.fi>,
Kees Cook <keescook@...omium.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v2 1/2] capabilities: Ambient capabilities
On Tue, May 19, 2015 at 1:22 PM, Aaron Jones <aaronmdjones@...il.com> wrote:
> On 19/05/15 20:07, Andy Lutomirski wrote:> It's in the cover letter,
> rather vaguely. I think I want to change
>> the setpriv syntax a bit before sending it upstream, though -- it's
>> sucks that you have to duplicate the option.
>>
>> Perhaps the ambient-caps option should implicitly raise inheritable
>> caps if they're not already raised. Or maybe the absence of an
>> inh-caps rule should cause any requested ambient caps to be made
>> inheritable as well.
>>
>> --Andy
>
> I propose an additional --ambient-inh option to copy everything from
> --inh-caps to the ambient set. Explicit is better than implicit.
Seems reasonable. I'll do something like that for v2.1.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists