[PATCH v12 11/11] seccomp: add thread sync ability
keescook at chromium.org
Fri Jul 18 11:58:52 PDT 2014
On Fri, Jul 18, 2014 at 11:51 AM, Andy Lutomirski <luto at amacapital.net> wrote:
> On Fri, Jul 18, 2014 at 11:13 AM, Kees Cook <keescook at chromium.org> wrote:
>> On Fri, Jul 18, 2014 at 10:17 AM, Andy Lutomirski <luto at amacapital.net> wrote:
>>> On Thu, Jul 17, 2014 at 8:26 PM, James Morris <jmorris at namei.org> wrote:
>>>> On Thu, 17 Jul 2014, Kees Cook wrote:
>>>>> Twelfth time's the charm! :)
>>>> Btw, there doesn't seem to be an official seccomp maintainer. Kees, would
>>>> you like to volunteer for this? If so, send in a patch for MAINTAINERS,
>>>> and set up a git tree for me to pull from.
>> Sure thing, I'll get this set up now. I wonder if I should include the
>> glob "arch/*/kernel/ptrace.c" in the MAINTAINERS entry. :P
> You might want to convince some arch maintainers first, and that's
> like herding cats. Or Oleg, at least. Also, do you really want to be
> asked to deal with the never-ending stream of bugs that people find in
> files matching that glob?
Yeah, I've opted for "K: \bsecure_computing" Seemed like a decent middle-ground.
>>> *snicker* :)
>>> Kees, if you take on this awesome responsibility, should I send you a
>>> rebased version of the fastpath stuff? If so, I think that the
>>> arch-neutral part should go in through your shiny new tree (once it's
>>> reviewed to your satisfaction), and I'll ask hpa to pick up the x86
>> Yeah, that sounds perfect.
>>> I'd volunteer to be a "R:eviewer", but I don't think that the R tag
>>> has made it into MAINTAINERS yet.
>> I'd love to have you listed. :)
> Feel free to pester me once "R" appears in case I forget.
I will indeed! :)
> You might be able to convince me to co-maintain some day. Hmm.
>> Kees Cook
>> Chrome OS Security
> Andy Lutomirski
> AMA Capital Management, LLC
Chrome OS Security
More information about the linux-arm-kernel